RCE via picklescan detection bypass for malicious pickle payloads
CVE-2025-71361 is a remote code execution vulnerability in picklescan before version 0.0.29. The issue is described as a detection bypass in which picklescan fails to identify malicious idlelib.calltip.Calltip.fetch_tip calls embedded in pickle files. As a result, an attacker can craft a pickle payload that passes scanning but still contains executable gadget behavior. If the resulting pickle is later deserialized with Python's pickle.load(), the embedded payload can execute arbitrary code. The vulnerable condition is therefore not in pickle deserialization itself, but in picklescan's incomplete detection logic for this malicious call pattern, which can cause defenders or downstream systems to incorrectly treat a malicious pickle as safe.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.