GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows attackers to forge arbitrary git-config directives by injecting equals signs, hash symbols, and whitespace into option names. Attackers can inject malicious option names like 'sshCommand = touch /tmp/RCE #' to execute arbitrary commands via core.sshCommand or core.hooksPath on the next git operation.
CVE-2026-76221
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026GitPython before 3.1.58 Config Injection via option-name | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-config-injection-via-option-namegit-config OPTION-name injection via =/#/whitespace bypasses name validator, enabling forged core.sshCommand/hooksPath (RCE) · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-jm78-9fvv-mhgrVendor Advisories for CVE-2026-76221(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gitpython | 0.1.7 ... 3.1.9 (110 versions) | 3.1.58 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 19:18 UTCEG score recompute
- 2026-08-20 19:18 UTCGHSA enrichment
- 2026-08-20 18:32 UTCEG score recompute
- 2026-08-20 18:32 UTCGHSA enrichment
- 2026-08-20 16:26 UTCGHSA enrichment
- 2026-08-20 04:19 UTCEG score recompute
- 2026-08-20 04:19 UTCGHSA enrichment
- 2026-08-20 04:08 UTCEG score recompute
- 2026-08-20 04:08 UTCGHSA enrichment
- 2026-08-20 02:36 UTCEG score recompute
- 2026-08-20 02:36 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-74
- CVE-2014-8423EG 10.0EPSS p99HIGH
- CVE-2015-10062NVD 5.5EG 9.8CRITICAL
- CVE-2015-10027NVD 5.5EG 9.8CRITICAL
- CVE-2016-15007NVD 5.5EG 9.8CRITICAL
- CVE-2016-15004NVD 7.3EG 9.8CRITICAL
- CVE-2013-4144EG 9.8CRITICAL
- CVE-2013-7487EG 9.8CRITICAL
- CVE-2014-4678EG 9.8EPSS p92CRITICAL
- CVE-2014-4967EG 9.8CRITICAL
- CVE-2014-4966EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-76221?
When was CVE-2026-76221 disclosed?
Is CVE-2026-76221 actively exploited?
What is the CVSS score of CVE-2026-76221?
How do I remediate CVE-2026-76221?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76221
Is Your Infrastructure Affected by CVE-2026-76221?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.