CVE-2026-67323
GitPython <3.1.51 allows command injection and file truncation via unsafe Repo APIs.
Is CVE-2026-67323 being exploited?
Not confirmed. CVE-2026-67323 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.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-67323?
CVE-2026-67323 is rated High with a CVSS score of 8.6. 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-67323?
Yes. A fix has been recorded for CVE-2026-67323. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67323 affect?
CVE-2026-67323 affects GitPython < 3.1.51, Python applications using GitPython Repo APIs, CI/CD tools and web apps embedding GitPython. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67323?
Upgrade to GitPython >=3.1.51 and validate/sanitize all git arguments.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote command execution via crafted Git options (e.g., --exec) and arbitrary file truncation via leading-dash revisions when apps pass attacker-controlled args.
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.