Vulnerability Description
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 check_unsafe_options guard present in the sibling iter_items 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).
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Gitpython Project | Gitpython | < 3.1.56 |
Related Weaknesses (CWE)
References
- https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-p538-ExploitVendor Advisory
- https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-truncation-Third Party Advisory
FAQ
What is CVE-2026-73621?
CVE-2026-73621 is a vulnerability with a CVSS score of 5.4 (MEDIUM). 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 check_unsafe_options guard present in ...
How severe is CVE-2026-73621?
CVE-2026-73621 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-73621?
Check the references section above for vendor advisories and patch information. Affected products include: Gitpython Project Gitpython.