GitPython before 3.1.51 contains an incomplete command injection blocklist that fails to account for git's long-option prefix abbreviation feature. Attackers can bypass the unsafe options guard by using abbreviated option names like upload_p instead of upload_pack, which git resolves to dangerous options and executes arbitrary commands.
CVE-2026-67325
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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(low)
- EG Risk
- 44(Track)EG Risk 44/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%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 1, 2026
Last Modified
August 1, 2026
Advisory Details (2)
Auto-updated Aug 1, 2026GitPython before 3.1.51 Command Injection via option prefix abbreviation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-command-injection-via-option-prefix-abbreviationCommand Injection via git long-option prefix abbreviation bypass of CVE-2026-42215 blocklist · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-2f96-g7mh-g2hxVendor Advisories for CVE-2026-67325(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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-01 13:19 UTCEG score recompute
- 2026-08-01 12:44 UTCEG score recompute
- 2026-08-01 12:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(4)
What is CVE-2026-67325?
When was CVE-2026-67325 disclosed?
What is the CVSS score of CVE-2026-67325?
How do I remediate CVE-2026-67325?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-67325
Is Your Infrastructure Affected by CVE-2026-67325?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.