CVE-2026-73621

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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).

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 computed
Severity54% × 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, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.56 Arbitrary File Truncation via Commit.count | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-truncation-via-commit-count
github Patch Available🟡 PoC Available

Arbitrary 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-8v24

Vendor 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)
PackageVulnerable rangeFixed inDependents
gitpython0.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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:12 UTCGHSA enrichment
  3. 2026-08-19 19:17 UTCEG score recompute
  4. 2026-08-19 19:17 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 19:14 UTCEG score recompute
  7. 2026-08-18 19:14 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 19:19 UTCEG score recompute
  11. 2026-08-17 19:19 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 19:25 UTCEG score recompute
  14. 2026-08-16 19:25 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 19:31 UTCEG score recompute
  19. 2026-08-15 19:31 UTCGHSA enrichment
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 19:36 UTCEG score recompute
  22. 2026-08-14 19:36 UTCGHSA enrichment
  23. 2026-08-14 18:34 UTCEG score recompute
  24. 2026-08-14 18:34 UTCGHSA enrichment
  25. 2026-08-14 17:08 UTCEG score recompute
Show 6 more
  1. 2026-08-14 17:08 UTCGHSA enrichment
  2. 2026-08-14 12:28 UTCGHSA enrichment
  3. 2026-08-13 12:33 UTCEG score recompute
  4. 2026-08-13 12:33 UTCGHSA enrichment
  5. 2026-08-13 11:42 UTCEG score recompute
  6. 2026-08-13 11:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73621?
CVE-2026-73621 is a medium vulnerability published on August 13, 2026. 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 iter_items method. An attacker who can control options passed to Commit.count (e.g., via…
When was CVE-2026-73621 disclosed?
CVE-2026-73621 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73621 actively exploited?
CVE-2026-73621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.9% of all scored CVEs.
What is the CVSS score of CVE-2026-73621?
CVE-2026-73621 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-73621?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73621, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73621

Explore →

Is Your Infrastructure Affected by CVE-2026-73621?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.