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=, causing 'git rev-list --output=' 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).
CVE-2026-73621
Score 5.4 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 13, 2026GitPython before 3.1.56 Arbitrary File Truncation via Commit.count | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-truncation-via-commit-countArbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-p538-c434-8v24Vendor Advisories for CVE-2026-73621(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gitpython | 0.1.7 ... 3.1.9 (108 versions) | 3.1.56 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 19:12 UTCGHSA enrichment
- 2026-08-19 19:17 UTCEG score recompute
- 2026-08-19 19:17 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:14 UTCEG score recompute
- 2026-08-18 19:14 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 19:19 UTCEG score recompute
- 2026-08-17 19:19 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 19:25 UTCEG score recompute
- 2026-08-16 19:25 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 19:31 UTCEG score recompute
- 2026-08-15 19:31 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:36 UTCEG score recompute
- 2026-08-14 19:36 UTCGHSA enrichment
- 2026-08-14 18:34 UTCEG score recompute
- 2026-08-14 18:34 UTCGHSA enrichment
- 2026-08-14 17:08 UTCEG score recompute
Show 6 moreShow fewer
- 2026-08-14 17:08 UTCGHSA enrichment
- 2026-08-14 12:28 UTCGHSA enrichment
- 2026-08-13 12:33 UTCEG score recompute
- 2026-08-13 12:33 UTCGHSA enrichment
- 2026-08-13 11:42 UTCEG score recompute
- 2026-08-13 11:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2007-0882EG 10.0EPSS p100HIGH
- CVE-2004-0480EG 10.0EPSS p95HIGH
- CVE-1999-0113EG 10.0EPSS p97HIGH
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS p95CRITICAL
- CVE-2020-21224EG 9.8EPSS p98CRITICAL
- CVE-2020-25494EG 9.8EPSS p98CRITICAL
- CVE-2020-15692EG 9.8EPSS p90CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS p100CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-73621?
When was CVE-2026-73621 disclosed?
Is CVE-2026-73621 actively exploited?
What is the CVSS score of CVE-2026-73621?
How do I remediate CVE-2026-73621?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73621
Is Your Infrastructure Affected by CVE-2026-73621?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.