CVE-2026-76220
Command execution in GitPython via crafted kwargs bypassing safety checks.
Is CVE-2026-76220 being exploited?
Not confirmed. CVE-2026-76220 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.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-76220?
CVE-2026-76220 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-76220?
Yes. A fix has been recorded for CVE-2026-76220. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76220 affect?
CVE-2026-76220 affects GitPython < 3.1.58, Python apps using GitPython (Repo.clone_from, clone_from, guarded APIs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76220?
Upgrade GitPython to >=3.1.58; block/untrusted inputs and audit code using clone APIs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary OS command execution via clone/guarded methods by supplying crafted kwargs that bypass check_unsafe_options.
Immediate action required
- affected< 3.1.58
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.