CVE-2026-114145: Standardebooks · GitPython validates a submodule's ".git" path only after cloning into it (RCE)
Affects standardebooksSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.1 soon.
Data as of 22 Nov 2026, 18:23 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 4.1.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 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 and applications should upgrade to version 4.1.1 or later to eliminate this vulnerability. Until upgrading, avoid passing untrusted or attacker-influenced submodule paths to create_submodule. Note that in versions 3.2.0 and later, although a ValueError is raised when an invalid path is detected, the malicious hook may already be planted on disk, so trapping the exception alone does not prevent exploitation.
Description
A vulnerability in GitPython's create_submodule function allows an attacker to execute arbitrary code by planting a malicious Git hook. The function clones a submodule into the repository's .git directory before validating the path, enabling an attacker to place an executable hook (e.g., post-checkout) in .git/hooks. This hook executes on subsequent Git operations, leading to code execution. Versions from 3.1.x through 3.2.0+ are affected, with 3.2.0+ raising a ValueError after cloning but not removing the planted hook. The issue is fixed in version 4.1.1.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-83vg-56qc-22m7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-114145 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2264 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/97eadb888d2f99567e3113f4e455be4ca128f697 (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.2.1 (opens in a new tab)