Loading vulnerability…
CVE-2026-73619 is an information disclosure vulnerability in GitPython before version 3.1.57. The flaw is caused by an incomplete denylist in the unsafe_git_archive_options guard used by Repo.archive(). Specifically, the guard fails to block archive-related options that permit adding attacker-chosen filesystem content to the generated archive. By supplying omitted archive options to Repo.archive(), an attacker can cause arbitrary local files to be read from the host filesystem and embedded in the returned archive. The issue is effectively a denylist bypass in GitPython's archive option validation and can expose sensitive files 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.