CVE-2026-73621
MEDIUMDescription
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).
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 10% of all known CVEs.
References
Related Vulnerabilities
Other CWE-88 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2016-10033 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-36804 | High | 8.8 | 99% | KEV | Fix |
| CVE-2026-24061 | Critical | 9.8 | 98% | KEV | Fix |
| CVE-2007-0882 | High | 10.0 | 98% | - | - |
| CVE-2018-17456 | Critical | 9.8 | 97% | - | Fix |
| CVE-2018-19518 | High | 7.5 | 95% | - | Fix |
Common questions
How do I fix CVE-2026-73621?
No published fix for CVE-2026-73621 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-73621 being actively exploited?
Not that we know of. CVE-2026-73621 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-73621?
CVE-2026-73621 has a CVSS v3 base score of 5.4, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-73621
Markdown
[](https://tridentstack.com/cve/CVE-2026-73621)HTML
<a href="https://tridentstack.com/cve/CVE-2026-73621"><img src="https://tridentstack.com/cve/badge/CVE-2026-73621.svg" alt="CVE-2026-73621"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-14.