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% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 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.3%CVSS: 7.8Exploit: Elevated riskExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.30-1 ... 3.1.62-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1 ... 3.1.62-2 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1
  • every version up to 3.1.50-1: fixed in 3.1.50-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython0.1.7 ... 3.1.9 (102 versions)
  • every version up to 3.1.50: fixed in 3.1.50
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 130× 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 325 total refreshes for this CVE.

  1. 2026-10-04 23:48 UTCEG score recompute
  2. 2026-10-04 23:48 UTCVendor advisory
  3. 2026-10-04 23:48 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 06:25 UTCEG score recompute
  6. 2026-10-04 06:25 UTCVendor advisory
  7. 2026-10-04 06:25 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 02:43 UTCEG score recompute
  10. 2026-10-03 02:43 UTCVendor advisory
  11. 2026-10-03 02:43 UTCGHSA enrichment
  12. 2026-10-02 17:56 UTCEPSS rescore
  13. 2026-10-02 10:28 UTCEG score recompute
  14. 2026-10-02 10:28 UTCVendor advisory
  15. 2026-10-02 10:28 UTCGHSA enrichment
  16. 2026-10-01 19:50 UTCEPSS rescore
  17. 2026-10-01 13:49 UTCVendor advisory
  18. 2026-10-01 13:49 UTCGHSA enrichment
  19. 2026-10-01 02:42 UTCEG score recompute
  20. 2026-10-01 02:42 UTCVendor advisory
  21. 2026-10-01 02:42 UTCGHSA enrichment
  22. 2026-09-30 15:03 UTCEPSS rescore
  23. 2026-09-29 06:46 UTCEG score recompute
  24. 2026-09-29 06:46 UTCVendor advisory
  25. 2026-09-29 06:46 UTCGHSA enrichment
Show 75 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 05:25 UTCVendor advisory
  3. 2026-09-28 05:25 UTCGHSA enrichment
  4. 2026-09-27 18:21 UTCEG score recompute
  5. 2026-09-27 18:21 UTCVendor advisory
  6. 2026-09-27 18:21 UTCGHSA enrichment
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 04:50 UTCEG score recompute
  10. 2026-09-25 04:50 UTCVendor advisory
  11. 2026-09-25 04:50 UTCGHSA enrichment
  12. 2026-09-24 08:29 UTCVendor advisory
  13. 2026-09-24 08:29 UTCGHSA enrichment
  14. 2026-09-23 21:25 UTCEG score recompute
  15. 2026-09-23 21:25 UTCVendor advisory
  16. 2026-09-23 21:25 UTCGHSA enrichment
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 08:42 UTCVendor advisory
  19. 2026-09-23 08:42 UTCGHSA enrichment
  20. 2026-09-22 21:32 UTCEG score recompute
  21. 2026-09-22 21:32 UTCVendor advisory
  22. 2026-09-22 21:32 UTCGHSA enrichment
  23. 2026-09-22 06:57 UTCEG score recompute
  24. 2026-09-22 06:57 UTCVendor advisory
  25. 2026-09-22 06:57 UTCGHSA enrichment
  26. 2026-09-20 20:59 UTCEG score recompute
  27. 2026-09-20 20:59 UTCVendor advisory
  28. 2026-09-20 20:59 UTCGHSA enrichment
  29. 2026-09-20 20:16 UTCEPSS rescore
  30. 2026-09-20 00:45 UTCEG score recompute
  31. 2026-09-20 00:45 UTCVendor advisory
  32. 2026-09-20 00:45 UTCGHSA enrichment
  33. 2026-09-19 13:41 UTCVendor advisory
  34. 2026-09-19 13:41 UTCGHSA enrichment
  35. 2026-09-19 00:24 UTCEG score recompute
  36. 2026-09-19 00:24 UTCVendor advisory
  37. 2026-09-19 00:23 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 13:20 UTCVendor advisory
  40. 2026-09-18 13:20 UTCGHSA enrichment
  41. 2026-09-18 01:14 UTCEG score recompute
  42. 2026-09-18 01:14 UTCVendor advisory
  43. 2026-09-18 01:14 UTCGHSA enrichment
  44. 2026-09-17 08:16 UTCVendor advisory
  45. 2026-09-17 08:16 UTCGHSA enrichment
  46. 2026-09-16 21:11 UTCEG score recompute▲ 0.80
  47. 2026-09-16 21:11 UTCVendor advisory
  48. 2026-09-16 21:11 UTCGHSA enrichment
  49. 2026-09-16 21:01 UTCNVD updateCVSS v3 → 7.8
  50. 2026-09-16 14:08 UTCEPSS rescore
  51. 2026-09-16 05:24 UTCEG score recompute
  52. 2026-09-16 05:24 UTCVendor advisory
  53. 2026-09-16 05:24 UTCGHSA enrichment
  54. 2026-09-16 05:15 UTCEPSS rescore
  55. 2026-09-15 02:55 UTCVendor advisory
  56. 2026-09-15 02:54 UTCGHSA enrichment
  57. 2026-09-14 12:15 UTCVendor advisory
  58. 2026-09-14 12:15 UTCGHSA enrichment
  59. 2026-09-14 01:08 UTCEG score recompute
  60. 2026-09-14 01:08 UTCVendor advisory
  61. 2026-09-14 01:08 UTCGHSA enrichment
  62. 2026-09-13 14:03 UTCVendor advisory
  63. 2026-09-13 14:03 UTCGHSA enrichment
  64. 2026-09-13 02:59 UTCVendor advisory
  65. 2026-09-13 02:59 UTCGHSA enrichment
  66. 2026-09-12 15:55 UTCEG score recompute
  67. 2026-09-12 15:55 UTCVendor advisory
  68. 2026-09-12 15:55 UTCGHSA enrichment
  69. 2026-09-12 04:51 UTCVendor advisory
  70. 2026-09-12 04:51 UTCGHSA enrichment
  71. 2026-09-11 17:47 UTCEG score recompute
  72. 2026-09-11 17:47 UTCVendor advisory
  73. 2026-09-11 17:47 UTCGHSA enrichment
  74. 2026-09-11 14:53 UTCEPSS rescore
  75. 2026-09-11 09:37 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 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.3% probability of exploitation in the next 30 days (15th percentile of EPSS-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?
A fix for CVE-2026-67326 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67326 are linked in the Vendor Advisories panel on this page.

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.