Loading vulnerability…
CVE-2026-4360 is an improper handling flaw in CPython's tarfile.TarFile.extract() method. When extracting a hardlink member, the supplied extraction filter is not propagated correctly. Consequently, an application that invokes extract() with filter='data' on an untrusted archive can extract files with uid/gid metadata that the data filter was intended to constrain.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Python 3.13 TAR-file handling vulnerability involving incorrect processing of user and group IDs.
A tarfile extraction vulnerability in which Tarfile.extract() does not properly pass the filter parameter when extracting hardlinks.
A tarfile extraction vulnerability in which Tarfile.extract() does not properly pass the filter parameter when extracting hardlinks.
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.