standardebooks · GitPython: clone_from()/clone() omit --separate-git-dir from unsafe_git_clone_options, enabling arbitrary
Affects standardebooksSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 4.1.0 soon.
Data as of 22 Nov 2026, 18:11 UTC
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade standardebooks to 4.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewstandardebookspkg:brew/standardebooksOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch fixing this vulnerability is available in GitPython version 4.1.0. Users and maintainers of applications using GitPython should upgrade to version 4.1.0 or later to ensure the `--separate-git-dir` option is properly blocked by default. Until upgrading, avoid passing `separate_git_dir` or `separate-git-dir` options to `Repo.clone_from()` or `Repo.clone()` unless `allow_unsafe_options=True` is explicitly required and carefully controlled. No other mitigation is documented or recommended by the vendor.
Description
GitPython versions from 2.9.2 up to but not including 4.1.0 contain a vulnerability where the `--separate-git-dir` option is not blocked by the unsafe options denylist in the `Repo.clone_from()` and `Repo.clone()` APIs. This omission allows an attacker to specify an arbitrary filesystem path for the Git metadata directory during a clone operation, potentially creating files and directories outside the intended clone destination. The vulnerability arises from a parity gap between denylist configurations for `git init` and `git clone` commands, despite documentation stating that `--separate-git-dir` should be blocked by default. A fix is available in GitPython version 4.1.0.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-8mcc-hrx5-hvxc (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-78677 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2210 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/b68afff45af0f49e79a3e2d2162018986b37ad5d (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.1.59 (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/gitpython/PYSEC-2026-3787.yaml (opens in a new tab)
- vulncheck.com/advisories/gitpython-before-path-traversal-via-separate-git-dir (opens in a new tab)