GitPython 3.1.50 fails to recognize joined short-option forms such as -u (the short form of --upload-pack=) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clone_from(..., multi_options=..., allow_unsafe_options=False), an attacker can supply -u to bypass the gate that blocks --upload-pack/-u, causing Git to execute the specified helper command during clone. Fixed in 3.1.51.
CVE-2026-67324
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-01. a secondary CVSS source baseline 9.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
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity98% × 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 3.1.50 Authentication Bypass via Joined Short Options | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-authentication-bypass-via-joined-short-optionsGitPython unsafe clone option gate bypass through joined short options · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-v396-v7q4-x2qjVendor Advisories for CVE-2026-67324(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 5× in last 7d / 5× 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 17:01 UTCEG score recompute
- 2026-08-01 17:01 UTCGHSA enrichment
- 2026-08-01 13:18 UTCEG score recompute
- 2026-08-01 12:43 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-67324?
When was CVE-2026-67324 disclosed?
What is the CVSS score of CVE-2026-67324?
How do I remediate CVE-2026-67324?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-67324
Is Your Infrastructure Affected by CVE-2026-67324?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.