Loading vulnerability…
CVE-2025-10155 is an improper input validation flaw in mmaitre314 picklescan affecting versions up to and including 0.0.30. Picklescan’s scanning logic can be bypassed by supplying a standard malicious Python pickle file while giving it a PyTorch-related filename extension such as .bin or .pt. Based on the provided content, Picklescan attempts PyTorch-specific parsing for such extensions, misclassifies the file, errors out, and fails to fall back to normal pickle analysis. As a result, the malicious pickle payload is incorrectly considered safe or left unscanned. If the file is later loaded by a consumer such as PyTorch or another Python component that deserializes the pickle content, attacker-controlled code can execute.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical Picklescan file-extension bypass vulnerability mentioned for background.
A vulnerability referenced as CVE-2025-10155. Details not specified in the content.
A Picklescan file-extension handling bypass that allows a malicious pickle payload to be treated as a safe PyTorch model file (e.g., .bin/.pt), enabling arbitrary code execution when the model is 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.