CVE-2026-100689: Standardebooks · GitPython submodule update path traversal can write outside the repository
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:23 UTC
- Patch
- Available – fixed in 4.1.1
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 26 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 patch is available in GitPython version 4.1.1 that applies the necessary containment checks to the 'path' field in submodule updates. Users should upgrade to version 4.1.1 or later to remediate this vulnerability. Until patched, avoid using submodule update operations on non-HEAD commits with untrusted .gitmodules files. The vendor advisory confirms the fix is included in 4.1.1.
Description
CVE-2026-100689 is a path traversal vulnerability in GitPython 3.1.61 and main branch affecting the handling of the .gitmodules 'path' field during submodule update operations. The vulnerability arises because the 'path' field is used without proper containment checks, allowing an attacker to specify a path outside the repository directory. This can lead to directory creation and file operations outside the intended repository scope. The issue primarily affects non-HEAD commit submodule updates, as normal clone operations do not expose this flaw. A fix is available in GitPython version 4.1.1.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-59cr-6r3x-644w (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2225 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/1ed0ebc2f2e74d979cdc367a4864a7731fdcc093 (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.1.62 (opens in a new tab)