CVE-2026-67326

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section headers into .git/config. Attackers can inject newlines to create a forged [core] section with hooksPath pointing to attacker-controlled directories, achieving remote code execution when git hooks are triggered.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 1, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.50 Newline Injection via config_writer section | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-newline-injection-via-config-writer-section
github Patch Available🟡 PoC Available

Newline injection in config_writer() section parameter bypasses CVE-2026-42215 patch, enabling RCE via core.hooksPath · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-mv93-w799-cj2w

Vendor Advisories for CVE-2026-67326(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatllvm21-main-21.1.8-8.hum12026-07-26redhat
redhatswift-lang-main-6.3.3-0.1.1.hum12026-07-25redhat
redhatllvm-main-22.1.8-4.1.hum12026-07-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.30-1 ... 3.1.61-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-13.1.50-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (102 versions)3.1.50—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 146× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 266 total refreshes for this CVE.

  1. 2026-09-19 00:24 UTCEG score recompute
  2. 2026-09-19 00:24 UTCVendor advisory
  3. 2026-09-19 00:23 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 13:20 UTCVendor advisory
  6. 2026-09-18 13:20 UTCGHSA enrichment
  7. 2026-09-18 01:14 UTCEG score recompute
  8. 2026-09-18 01:14 UTCVendor advisory
  9. 2026-09-18 01:14 UTCGHSA enrichment
  10. 2026-09-17 08:16 UTCVendor advisory
  11. 2026-09-17 08:16 UTCGHSA enrichment
  12. 2026-09-16 21:11 UTCEG score recompute▲ 0.80
  13. 2026-09-16 21:11 UTCVendor advisory
  14. 2026-09-16 21:11 UTCGHSA enrichment
  15. 2026-09-16 21:01 UTCNVD updateCVSS v3 → 7.8
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:24 UTCEG score recompute
  18. 2026-09-16 05:24 UTCVendor advisory
  19. 2026-09-16 05:24 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 02:55 UTCVendor advisory
  22. 2026-09-15 02:54 UTCGHSA enrichment
  23. 2026-09-14 12:15 UTCVendor advisory
  24. 2026-09-14 12:15 UTCGHSA enrichment
  25. 2026-09-14 01:08 UTCEG score recompute
Show 75 more
  1. 2026-09-14 01:08 UTCVendor advisory
  2. 2026-09-14 01:08 UTCGHSA enrichment
  3. 2026-09-13 14:03 UTCVendor advisory
  4. 2026-09-13 14:03 UTCGHSA enrichment
  5. 2026-09-13 02:59 UTCVendor advisory
  6. 2026-09-13 02:59 UTCGHSA enrichment
  7. 2026-09-12 15:55 UTCEG score recompute
  8. 2026-09-12 15:55 UTCVendor advisory
  9. 2026-09-12 15:55 UTCGHSA enrichment
  10. 2026-09-12 04:51 UTCVendor advisory
  11. 2026-09-12 04:51 UTCGHSA enrichment
  12. 2026-09-11 17:47 UTCEG score recompute
  13. 2026-09-11 17:47 UTCVendor advisory
  14. 2026-09-11 17:47 UTCGHSA enrichment
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-11 06:21 UTCVendor advisory
  18. 2026-09-11 06:21 UTCGHSA enrichment
  19. 2026-09-10 19:16 UTCEG score recompute
  20. 2026-09-10 19:16 UTCVendor advisory
  21. 2026-09-10 19:16 UTCGHSA enrichment
  22. 2026-09-10 08:11 UTCVendor advisory
  23. 2026-09-10 08:10 UTCGHSA enrichment
  24. 2026-09-09 21:06 UTCEG score recompute
  25. 2026-09-09 21:06 UTCVendor advisory
  26. 2026-09-09 21:05 UTCGHSA enrichment
  27. 2026-09-09 19:44 UTCVendor advisory
  28. 2026-09-09 19:44 UTCGHSA enrichment
  29. 2026-09-09 06:56 UTCEG score recompute
  30. 2026-09-09 06:56 UTCVendor advisory
  31. 2026-09-09 06:56 UTCGHSA enrichment
  32. 2026-09-08 22:01 UTCEPSS rescore
  33. 2026-09-07 19:15 UTCEG score recompute
  34. 2026-09-07 19:15 UTCVendor advisory
  35. 2026-09-07 19:15 UTCGHSA enrichment
  36. 2026-09-07 16:01 UTCEPSS rescore
  37. 2026-09-06 16:52 UTCEG score recompute
  38. 2026-09-06 16:52 UTCVendor advisory
  39. 2026-09-06 16:52 UTCGHSA enrichment
  40. 2026-09-06 13:47 UTCEPSS rescore
  41. 2026-09-06 05:48 UTCVendor advisory
  42. 2026-09-06 05:47 UTCGHSA enrichment
  43. 2026-09-05 18:43 UTCEG score recompute
  44. 2026-09-05 18:43 UTCVendor advisory
  45. 2026-09-05 18:43 UTCGHSA enrichment
  46. 2026-09-05 15:31 UTCEPSS rescore
  47. 2026-09-05 04:36 UTCEG score recompute
  48. 2026-09-05 04:36 UTCVendor advisory
  49. 2026-09-05 04:36 UTCGHSA enrichment
  50. 2026-09-04 10:25 UTCEG score recompute
  51. 2026-09-04 10:25 UTCVendor advisory
  52. 2026-09-04 10:25 UTCGHSA enrichment
  53. 2026-09-04 05:07 UTCEPSS rescore
  54. 2026-09-03 20:45 UTCVendor advisory
  55. 2026-09-03 20:45 UTCGHSA enrichment
  56. 2026-09-03 09:03 UTCEG score recompute
  57. 2026-09-03 09:03 UTCVendor advisory
  58. 2026-09-03 09:02 UTCGHSA enrichment
  59. 2026-09-02 14:12 UTCEPSS rescore
  60. 2026-09-01 22:23 UTCEG score recompute
  61. 2026-09-01 22:23 UTCVendor advisory
  62. 2026-09-01 22:23 UTCGHSA enrichment
  63. 2026-09-01 13:54 UTCEPSS rescore
  64. 2026-09-01 04:40 UTCEPSS rescore
  65. 2026-08-31 23:19 UTCEG score recompute
  66. 2026-08-31 23:19 UTCVendor advisory
  67. 2026-08-31 23:19 UTCGHSA enrichment
  68. 2026-08-30 21:13 UTCEG score recompute
  69. 2026-08-30 21:13 UTCVendor advisory
  70. 2026-08-30 21:13 UTCGHSA enrichment
  71. 2026-08-30 19:17 UTCEPSS rescore
  72. 2026-08-30 10:09 UTCEG score recompute
  73. 2026-08-30 10:09 UTCVendor advisory
  74. 2026-08-30 10:09 UTCGHSA enrichment
  75. 2026-08-30 01:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-67326?
CVE-2026-67326 is a high vulnerability published on August 1, 2026. GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section headers into .git/config. Attackers can inject newlines to create a forged [core] section with hooksPath pointing to attacker-controlled…
When was CVE-2026-67326 disclosed?
CVE-2026-67326 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67326 actively exploited?
CVE-2026-67326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-67326?
CVE-2026-67326 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-67326?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67326, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67326

Explore →

Is Your Infrastructure Affected by CVE-2026-67326?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs