CVE-2026-67326

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this weekElevated
7.0EG
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.0Exploit: 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.0
EG Score
7.0(high)
EG Risk
48(Track*)
EG Risk 48/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
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 14, 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.50-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-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 44× in last 7d / 126× 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 126 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 14, 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 90.8% of all scored CVEs.
What is the CVSS score of CVE-2026-67326?
CVE-2026-67326 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
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