CVE-2026-87817: GitPython · Repository content can impersonate the git directory, leading to arbitrary code execution
Affects standardebooksSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 4.1.1 soon.
Data as of 22 Nov 2026, 18:11 UTC
- Patch
- Available – fixed in 4.1.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 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.1.
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 fix is available in GitPython version 4.1.1. Users should upgrade to this version or later to resolve the vulnerability. The fix involves reordering the git directory discovery to prioritize the real .git directory, validating HEAD contents, resolving hook paths correctly, and disabling merge_includes when reading config. Until upgrading, users should avoid opening or cloning untrusted repositories with GitPython and avoid calling index.commit() on such repositories.
Description
GitPython versions from 2.9.2 up to but not including 4.1.1 contain a vulnerability where the library misidentifies the git directory by prioritizing tracked files over the actual .git directory. This allows attacker-controlled repository content to impersonate the git directory, leading to arbitrary code execution via malicious hooks when a victim performs a commit using GitPython. Additionally, attackers can read sensitive files outside the repository and write config files to arbitrary locations. The issue is fixed in version 4.1.1.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-239g-whfq-7xj9 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-87817 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2218 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/c7cf4d13b1ed0a2e70f2a1f3c6b4fc6c2652cf0b (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.1.60 (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/gitpython/PYSEC-2026-3982.yaml (opens in a new tab)
- vulncheck.com/advisories/gitpython-before-3.1.60-remote-code-execution-via-git-directory-impersonation (opens in a new tab)