CVE-2026-67325
GitPython command injection via abbreviated git long-option bypass.
Is CVE-2026-67325 being exploited?
Not confirmed. CVE-2026-67325 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 1.9% probability of exploitation in the next 30 days.
How severe is CVE-2026-67325?
CVE-2026-67325 is rated High with a CVSS score of 8.7. 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-67325?
Yes. A fix has been recorded for CVE-2026-67325. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67325 affect?
CVE-2026-67325 affects GitPython <3.1.51, Applications and CI/CD tooling that call GitPython with user-controlled args. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67325?
Upgrade to GitPython >=3.1.51 and sanitize or disallow untrusted git arguments.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary command execution by bypassing GitPython's unsafe-options guard using abbreviated git long-options.
Immediate action required
- affected< 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.