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
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- 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
- 41%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
September 2, 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(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | python3.12-gitpython-0:3.1.59-1.el9pc | 2026-09-03 | redhat |
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
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.30-1 ... 3.1.61-1 (11 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1 | 3.1.61-1 | — |
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 37× in last 7d / 140× 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 149 total refreshes for this CVE.
- 2026-09-18 21:48 UTCEG score recompute
- 2026-09-18 21:48 UTCVendor advisory
- 2026-09-18 21:48 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 09:41 UTCVendor advisory
- 2026-09-18 09:41 UTCGHSA enrichment
- 2026-09-17 21:34 UTCEG score recompute
- 2026-09-17 21:34 UTCVendor advisory
- 2026-09-17 21:34 UTCGHSA enrichment
- 2026-09-17 08:15 UTCVendor advisory
- 2026-09-17 08:15 UTCGHSA enrichment
- 2026-09-16 20:08 UTCEG score recompute
- 2026-09-16 20:08 UTCVendor advisory
- 2026-09-16 20:08 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:45 UTCVendor advisory
- 2026-09-16 04:45 UTCGHSA enrichment
- 2026-09-15 16:17 UTCVendor advisory
- 2026-09-15 16:17 UTCGHSA enrichment
- 2026-09-15 04:10 UTCEG score recompute
- 2026-09-15 04:10 UTCVendor advisory
- 2026-09-15 04:10 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 16:02 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-14 16:02 UTCGHSA enrichment
- 2026-09-14 03:55 UTCEG score recompute
- 2026-09-14 03:55 UTCVendor advisory
- 2026-09-14 03:55 UTCGHSA enrichment
- 2026-09-13 15:48 UTCVendor advisory
- 2026-09-13 15:48 UTCGHSA enrichment
- 2026-09-13 03:39 UTCVendor advisory
- 2026-09-13 03:39 UTCGHSA enrichment
- 2026-09-12 15:32 UTCEG score recompute
- 2026-09-12 15:32 UTCVendor advisory
- 2026-09-12 15:32 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-12 03:25 UTCVendor advisory
- 2026-09-12 03:25 UTCGHSA enrichment
- 2026-09-11 15:17 UTCEG score recompute
- 2026-09-11 15:17 UTCVendor advisory
- 2026-09-11 15:17 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 03:09 UTCVendor advisory
- 2026-09-11 03:09 UTCGHSA enrichment
- 2026-09-10 15:02 UTCEG score recompute
- 2026-09-10 15:02 UTCVendor advisory
- 2026-09-10 15:02 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 02:55 UTCVendor advisory
- 2026-09-10 02:55 UTCGHSA enrichment
- 2026-09-09 14:47 UTCVendor advisory
- 2026-09-09 14:47 UTCGHSA enrichment
- 2026-09-09 02:40 UTCEG score recompute
- 2026-09-09 02:40 UTCVendor advisory
- 2026-09-09 02:40 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:08 UTCEG score recompute
- 2026-09-07 22:08 UTCVendor advisory
- 2026-09-07 22:08 UTCGHSA enrichment
- 2026-09-07 10:01 UTCVendor advisory
- 2026-09-07 10:01 UTCGHSA enrichment
- 2026-09-06 21:45 UTCEG score recompute
- 2026-09-06 21:45 UTCVendor advisory
- 2026-09-06 21:45 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 09:37 UTCVendor advisory
- 2026-09-06 09:37 UTCGHSA enrichment
- 2026-09-05 21:30 UTCEG score recompute
- 2026-09-05 21:30 UTCVendor advisory
- 2026-09-05 21:30 UTCGHSA enrichment
- 2026-09-05 09:23 UTCVendor advisory
- 2026-09-05 09:23 UTCGHSA enrichment
- 2026-09-04 21:16 UTCEG score recompute
- 2026-09-04 21:16 UTCVendor advisory
- 2026-09-04 21:15 UTCGHSA enrichment
- 2026-09-04 08:22 UTCEG score recompute
- 2026-09-04 08:21 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 20:14 UTCGHSA enrichment
- 2026-09-03 08:04 UTCGHSA enrichment
- 2026-09-02 19:51 UTCEG score recompute
- 2026-09-02 19:51 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 09:19 UTCGHSA enrichment
- 2026-09-01 21:12 UTCEG score recompute
- 2026-09-01 21:12 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 08:59 UTCEG score recompute
- 2026-09-01 08:59 UTCGHSA enrichment
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 20:41 UTCGHSA enrichment
- 2026-08-31 14:58 UTCGHSA enrichment
- 2026-08-31 02:52 UTCEG score recompute
- 2026-08-31 02:52 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 14:44 UTCGHSA enrichment
- 2026-08-30 02:37 UTCEG score recompute
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.