Skip to main content
CVE-2026-73621VulnerabilityPublished Updated

standardebooks · GitPython: Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-73621· Medium 5.3

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

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewstandardebookspkg:brew/standardebooksOther threatsAffected
  • >=2.9.2 <4.1.0
Fixed in
  • 4.1.0

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

Community reviews

Loading reviews…