CVE-2026-78675
GitPython .gitmodules include parsing can leak local file contents
Is CVE-2026-78675 being exploited?
Not confirmed. CVE-2026-78675 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.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-78675?
CVE-2026-78675 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-78675?
Yes. A fix has been recorded for CVE-2026-78675. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-78675 affect?
CVE-2026-78675 affects GitPython < 3.1.59, Python applications using GitPython, CI/CD tools using GitPython, Developer workstations running affected code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-78675?
Upgrade GitPython to >=3.1.59 and validate .gitmodules handling
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local file disclosure: crafted .gitmodules with [include] can cause repo.submodules parsing to leak arbitrary local file lines in exception messages.
Patch when possible
- 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.