Loading vulnerability…
CVE-2026-73621 is an argument injection vulnerability in GitPython before version 3.1.56. The flaw is in the Commit.count() method, which forwards attacker-controlled keyword arguments to the underlying 'git rev-list' invocation without applying the unsafe-option validation used by the related iter_items method. If an application passes user-influenced options into Commit.count(), an attacker can inject supported rev-list options such as an output parameter that causes Git to open and truncate a chosen file before revision parsing completes. The issue does not provide arbitrary file content control, but it does permit destructive zero-byte truncation of a file accessible to the running process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.