GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution.
CVE-2026-78677
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026GitPython before 3.1.59 Path Traversal via separate-git-dir | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-path-traversal-via-separate-git-dirclone_from()/clone() omit --separate-git-dir from unsafe_git_clone_options, enabling arbitrary git-directory creation outside the destination · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-8mcc-hrx5-hvxcVendor Advisories for CVE-2026-78677(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 26× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 02:09 UTCEG score recompute
- 2026-08-30 02:09 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 13:14 UTCGHSA enrichment
- 2026-08-29 00:18 UTCEG score recompute
- 2026-08-29 00:18 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 09:08 UTCGHSA enrichment
- 2026-08-27 20:13 UTCEG score recompute
- 2026-08-27 20:12 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 07:13 UTCGHSA enrichment
- 2026-08-26 18:18 UTCEG score recompute
- 2026-08-26 18:17 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 05:21 UTCGHSA enrichment
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 16:24 UTCGHSA enrichment
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:30 UTCGHSA enrichment
- 2026-08-25 15:16 UTCEG score recompute
- 2026-08-25 15:16 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-78677?
When was CVE-2026-78677 disclosed?
Is CVE-2026-78677 actively exploited?
What is the CVSS score of CVE-2026-78677?
How do I remediate CVE-2026-78677?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78677
Is Your Infrastructure Affected by CVE-2026-78677?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.