CVE-2026-73621: GitPython before 3.1.56 Arbitrary File Truncation via Commit.count
GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the checkunsafeoptions guard present in the sibling iteritems method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73621?
CVE-2026-73621 has a medium severity score of 5.4.
What is the risk level associated with CVE-2026-73621?
CVE-2026-73621 has a risk level of 34.
How do I fix CVE-2026-73621?
To fix CVE-2026-73621, upgrade GitPython to version 3.1.56 or later.
What vulnerability does CVE-2026-73621 address?
CVE-2026-73621 addresses an argument injection vulnerability in the Commit.count() method of GitPython.
What potential impact does CVE-2026-73621 pose?
CVE-2026-73621 allows for arbitrary file truncation when untrusted options are passed to Commit.count.