CVE-2026-78677
Path traversal via Repo.clone separate_git_dir allows creating git dirs outside target.
Is CVE-2026-78677 being exploited?
Not confirmed. CVE-2026-78677 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-78677?
CVE-2026-78677 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-78677?
Yes. A fix has been recorded for CVE-2026-78677. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-78677 affect?
CVE-2026-78677 affects GitPython < 3.1.59, Python apps using Repo.clone_from/Repo.clone, CI/CD pipelines, Developer workstations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-78677?
Upgrade to GitPython >=3.1.59; validate clone inputs and restrict filesystem permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can create arbitrary git metadata dirs outside the clone target and may trigger repository hooks, enabling arbitrary code execution or persistence.
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.