standardebooks · GitPython: Arbitrary local file content disclosure via [include] directive in untrusted .gitmodules
Affects standardebooksSource GCVE Database
Not known to be exploited · CVSS 8.6 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:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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 is available in GitPython version 4.1.0 that disables merge_includes in the SubmoduleConfigParser to prevent following untrusted [include] directives in .gitmodules. Users should upgrade to version 4.1.0 or later. Until upgraded, avoid processing untrusted repositories with GitPython or handle exceptions from repo.submodules carefully to avoid leaking file contents.
Description
GitPython versions from 2.9.2 up to but not including 4.1.0 contain a vulnerability in the handling of the .gitmodules file, where the SubmoduleConfigParser follows [include] directives without restricting paths. This allows an attacker controlling the .gitmodules file to cause the parser to read arbitrary local files and expose their first line via exception messages. The issue arises because merge_includes is enabled by default and no containment checks are performed on included paths. A fix is available in version 4.1.0.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-7833-fr7j-v32q (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-78675 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2211 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/ef7568e3b317ce617eacda39b8b54dcdff8c3b5c (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-3785.yaml (opens in a new tab)
- vulncheck.com/advisories/gitpython-before-local-file-content-disclosure-via-gitmodules (opens in a new tab)