Loading vulnerability…
CVE-2025-10156 is a critical vulnerability in the ZIP archive scanning component of mmaitre314 Picklescan. By crafting a ZIP archive that contains a file with an invalid Cyclic Redundancy Check (CRC) value, an attacker can trigger an exceptional condition that causes Picklescan to halt or fail before fully analyzing the archive contents for malicious pickle payloads. As a result, a malicious PyTorch model or other ZIP-packaged artifact containing unsafe pickle content may evade detection and be incorrectly treated as safe. The issue is described as affecting Picklescan’s ZIP handling logic, with referenced vulnerable code in relaxed_zipfile.py in v0.0.29.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical Picklescan ZIP archive bypass vulnerability mentioned for background.
A vulnerability referenced as CVE-2025-10156. Details not specified in the content.
A Picklescan ZIP scanning bypass where a crafted CRC error prevents proper archive scanning, allowing malicious model content to evade detection and later execute when loaded.
A critical security bypass vulnerability in mmaitre314 picklescan's ZIP archive scanning component that can be triggered with a malformed ZIP containing a bad CRC, causing scanning to halt and potentially allowing malicious pickle files to evade detection and lead to code execution when loaded.
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.