CVE-2025-10157 is a critical protection mechanism failure in mmaitre314 PickleScan affecting versions up to and including 0.0.30. PickleScan’s unsafe-globals detection relies on exact module-name matching in its blocklist logic. An attacker can evade this check by referencing a dangerous package through a submodule path rather than the exact blocked module name, for example using a submodule such as 'asyncio.unix_events' instead of 'asyncio'. As a result, a malicious pickle payload embedded in a pickle file or PyTorch model artifact can be misclassified as merely suspicious or effectively treated as safe during scanning. If the artifact is subsequently loaded by Python or PyTorch, the embedded pickle payload can execute attacker-controlled code.
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 blocklist-bypass vulnerability mentioned for background.
A vulnerability in Picklescan. Details not specified in the content.
A Picklescan unsafe-globals/blocklist bypass that permits dangerous imports/operations to evade detection, resulting in arbitrary code execution when the malicious pickle payload is deserialized/loaded.
A critical protection mechanism failure in mmaitre314 picklescan up to and including version 0.0.30 that allows bypass of the unsafe globals check via submodule imports, potentially leading to malicious code execution when a scanned file is later 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.