CVE-2026-78676
GitPython config-write bug enables RCE by turning quoted values into active git directives
Is CVE-2026-78676 being exploited?
Not confirmed. CVE-2026-78676 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-78676?
CVE-2026-78676 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-78676?
Yes. A fix has been recorded for CVE-2026-78676. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-78676 affect?
CVE-2026-78676 affects GitPython < 3.1.59, Python apps using GitPython for git-config writes, CI/CD systems and developer tooling using GitPython, Build agents and automation scripts bundling GitPython. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-78676?
Upgrade to GitPython >= 3.1.59; inspect and sanitize git-config files and CI/CD agents
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution: crafted git-config with embedded newlines is re-serialized into directives (e.g., core.hooksPath), triggering malicious hooks on GitPython config write.
Immediate action required
- affected< 3.1.59
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.