CVE-2026-73621

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM 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(medium)
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
12%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 3, 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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.30-1 ... 3.1.61-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-13.1.61-1—
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 18× in last 7d / 79× 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.

Showing the most recent 100 of 108 total refreshes for this CVE.

  1. 2026-09-19 04:49 UTCEG score recompute
  2. 2026-09-19 04:49 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 04:53 UTCEG score recompute
  5. 2026-09-18 04:53 UTCGHSA enrichment
  6. 2026-09-17 04:58 UTCEG score recompute
  7. 2026-09-17 04:58 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-16 05:03 UTCGHSA enrichment
  11. 2026-09-15 04:35 UTCEG score recompute
  12. 2026-09-15 04:35 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 04:40 UTCEG score recompute
  15. 2026-09-14 04:40 UTCGHSA enrichment
  16. 2026-09-13 04:46 UTCEG score recompute
  17. 2026-09-13 04:46 UTCGHSA enrichment
  18. 2026-09-12 15:02 UTCEPSS rescore
  19. 2026-09-12 04:51 UTCEG score recompute
  20. 2026-09-12 04:51 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 04:56 UTCEG score recompute
  23. 2026-09-11 04:56 UTCGHSA enrichment
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-10 05:01 UTCGHSA enrichment
Show 75 more
  1. 2026-09-09 05:06 UTCEG score recompute
  2. 2026-09-09 05:06 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:38 UTCEG score recompute
  5. 2026-09-07 16:38 UTCGHSA enrichment
  6. 2026-09-06 16:02 UTCEG score recompute
  7. 2026-09-06 16:02 UTCGHSA enrichment
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-05 16:08 UTCEG score recompute
  10. 2026-09-05 16:08 UTCGHSA enrichment
  11. 2026-09-04 16:13 UTCEG score recompute
  12. 2026-09-04 16:13 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 16:18 UTCGHSA enrichment
  15. 2026-09-02 23:20 UTCEG score recompute
  16. 2026-09-02 23:20 UTCGHSA enrichment
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 20:29 UTCEG score recompute
  19. 2026-09-01 20:29 UTCGHSA enrichment
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-31 20:34 UTCGHSA enrichment
  24. 2026-08-31 09:49 UTCEG score recompute
  25. 2026-08-31 09:49 UTCGHSA enrichment
  26. 2026-08-30 19:18 UTCEPSS rescore
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 08:13 UTCEG score recompute
  29. 2026-08-30 08:13 UTCGHSA enrichment
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-29 08:19 UTCEG score recompute
  32. 2026-08-29 08:19 UTCGHSA enrichment
  33. 2026-08-28 21:42 UTCEPSS rescore
  34. 2026-08-27 19:34 UTCEG score recompute
  35. 2026-08-27 19:34 UTCGHSA enrichment
  36. 2026-08-27 14:25 UTCEPSS rescore
  37. 2026-08-26 18:46 UTCEG score recompute
  38. 2026-08-26 18:46 UTCGHSA enrichment
  39. 2026-08-26 14:47 UTCEPSS rescore
  40. 2026-08-25 18:45 UTCEG score recompute
  41. 2026-08-25 18:45 UTCGHSA enrichment
  42. 2026-08-25 13:49 UTCEPSS rescore
  43. 2026-08-24 18:50 UTCEG score recompute
  44. 2026-08-24 18:50 UTCGHSA enrichment
  45. 2026-08-23 18:56 UTCEG score recompute
  46. 2026-08-23 18:56 UTCGHSA enrichment
  47. 2026-08-23 00:19 UTCEPSS rescore
  48. 2026-08-22 19:02 UTCEG score recompute
  49. 2026-08-22 19:02 UTCGHSA enrichment
  50. 2026-08-21 23:49 UTCEPSS rescore
  51. 2026-08-21 19:07 UTCEG score recompute
  52. 2026-08-21 19:07 UTCGHSA enrichment
  53. 2026-08-20 22:56 UTCEPSS rescore
  54. 2026-08-20 19:12 UTCGHSA enrichment
  55. 2026-08-19 19:17 UTCEG score recompute
  56. 2026-08-19 19:17 UTCGHSA enrichment
  57. 2026-08-19 17:04 UTCEPSS rescore
  58. 2026-08-18 19:14 UTCEG score recompute
  59. 2026-08-18 19:14 UTCGHSA enrichment
  60. 2026-08-18 13:49 UTCEPSS rescore
  61. 2026-08-18 13:49 UTCEPSS rescore
  62. 2026-08-17 19:19 UTCEG score recompute
  63. 2026-08-17 19:19 UTCGHSA enrichment
  64. 2026-08-17 13:47 UTCEPSS rescore
  65. 2026-08-16 19:25 UTCEG score recompute
  66. 2026-08-16 19:25 UTCGHSA enrichment
  67. 2026-08-16 14:56 UTCEPSS rescore
  68. 2026-08-16 14:56 UTCEPSS rescore
  69. 2026-08-16 02:15 UTCEPSS rescore
  70. 2026-08-15 19:31 UTCEG score recompute
  71. 2026-08-15 19:31 UTCGHSA enrichment
  72. 2026-08-15 01:31 UTCEPSS rescore
  73. 2026-08-14 19:36 UTCEG score recompute
  74. 2026-08-14 19:36 UTCGHSA enrichment
  75. 2026-08-14 18:34 UTCEG score recompute

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 September 3, 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 88.3% 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.

Start Free Scan →Browse All CVEs