MEDIUMUnknown →
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 sep
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.
Affected packages
No package-level mapping for this advisory.
Exploit signal
- Known exploited (CISA KEV)
- No
- EPSS score
- —
- EPSS percentile
- —
EPSS is the probability a CVE is exploited in the wild; percentile is its rank among all CVEs.
Sources
- https://www.cve.org/CVERecord?id=CVE-2026-78677
- https://github.com/cveproject/cvelistv5/tree/main/cves/2026/78xxx/cve-2026-78677.json
- https://github.com/gitpython-developers/gitpython/security/advisories/ghsa-8mcc-hrx5-hvxc
- https://nvd.nist.gov/vuln/detail/cve-2026-78677
- https://www.vulncheck.com/advisories/gitpython-before-path-traversal-via-separate-git-dir
Structured record: https://ubuntu.com/security/CVE-2026-78677
Recommended response stack
Snyk — Scan your dependencies in CI and fix this vulnerability.→Socket — Detect malicious and compromised packages before they ship.→
Some links are affiliate links — HackTribune may earn a commission at no extra cost to you.
Get incidents like this as alerts for your stack.
Join the beta