CVE-2026-76221
GitPython config-name injection enables command execution via crafted option names
Is CVE-2026-76221 being exploited?
Not confirmed. CVE-2026-76221 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-76221?
CVE-2026-76221 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-76221?
Yes. A fix has been recorded for CVE-2026-76221. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76221 affect?
CVE-2026-76221 affects GitPython < 3.1.58, Python apps using GitPython, CI/CD systems processing untrusted repositories. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76221?
Upgrade to GitPython >=3.1.58 and avoid processing untrusted repositories
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution: attackers can inject git-config option names to set core.sshCommand or core.hooksPath, executing commands on next git operation.
Patch when possible
- 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.