CVE-2026-67324
GitPython option-parsing flaw allows attacker-supplied -u helper to execute during clone.
Is CVE-2026-67324 being exploited?
Not confirmed. CVE-2026-67324 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-67324?
CVE-2026-67324 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67324?
Yes. A fix has been recorded for CVE-2026-67324. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67324 affect?
CVE-2026-67324 affects GitPython 3.1.50, Python apps using Repo.clone_from(..., multi_options=...), CI/CD and code-management tools invoking GitPython. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67324?
Upgrade to GitPython 3.1.51 and stop accepting untrusted multi_options.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution: attacker can supply -u<helper> in clone options to run arbitrary helper commands on host when apps pass untrusted multi_options.
Immediate action required
- affected>= 3.1.50 and < 3.1.51
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.