Arbitrary file truncation via unguarded Commit.count options
Published Aug 13, 2026 · Updated Aug 13, 2026
Argument injection in GitPython before 3.1.56 allows remote authenticated users to truncate arbitrary files through Commit.count options. Commit.count forwards keyword arguments to git rev-list without the unsafe-option check used by sibling revision APIs, so output= opens and zeroes that path. Exploitation requires an application to pass attacker-controlled option keys; affected files are reduced to zero bytes at the process privilege level.
Summary
What happened
Argument injection in GitPython before 3.1.56 allows remote authenticated users to truncate arbitrary files through Commit.count options. Commit.count forwards keyword arguments to git rev-list without the unsafe-option check used by sibling revision APIs, so output= opens and zeroes that path. Exploitation requires an application to pass attacker-controlled option keys; affected files are reduced to zero bytes at the process privilege level.
The record
- CVE
- CVE-2026-73621
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- GitPython Developers
- Product
- GitPython
- Classifications
- CWE-88, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.56
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Commit.count output-option truncation proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo