standardebooks · GitPython: Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count
Affects standardebooksSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.1.0 when convenient.
Data as of 22 Nov 2026, 18:12 UTC
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 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 adds the missing check_unsafe_options guard to Commit.count(), preventing unsafe output parameters from being passed to git rev-list. Users should upgrade to version 4.1.0 or later to remediate this vulnerability. Until upgraded, avoid passing untrusted or user-controlled output parameters to Commit.count().
Description
GitPython versions from 2.9.2 up to 4.1.0 contain a vulnerability in the Commit.count() method where unsafe options are forwarded to the underlying git rev-list command without proper validation. This allows an attacker with the ability to influence the output parameter to cause git rev-list to truncate an arbitrary file to zero bytes, resulting in file destruction. The vulnerability is due to missing checks for unsafe options in Commit.count(), unlike the sibling iter_items method which has such protections. The issue was fixed in version 4.1.0 by adding appropriate checks.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-p538-c434-8v24 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2184 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/38553b6fddc7f6a667cdb45a6762343a08fc72b2 (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.1.56 (opens in a new tab)