Remote code execution via undetected runcode reduction
Published Jul 4, 2026 · Updated Jul 4, 2026
Scanner bypass in picklescan before 0.0.30 allows remote attackers to conceal code execution in malicious pickle files. Its global-call analysis fails to flag a reduce method that returns idlelib.run.Executive.runcode with attacker-controlled Python source. Execution requires a user or service to trust the clean scan result and load the pickle, after which runcode evaluates the embedded source in the loader process.
Summary
What happened
Scanner bypass in picklescan before 0.0.30 allows remote attackers to conceal code execution in malicious pickle files. Its global-call analysis fails to flag a reduce method that returns idlelib.run.Executive.runcode with attacker-controlled Python source. Execution requires a user or service to trust the clean scan result and load the pickle, after which runcode evaluates the embedded source in the loader process.
The record
- CVE
- CVE-2025-71342
- Published
- Jul 4, 2026
- Updated
- Jul 4, 2026
- Vendor
- Matthieu Maitre
- Product
- picklescan
- Classifications
- CWE-502, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 4, 2026CVE publishedPublication date reported by the CVE source.
- Jul 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.0.30
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Executive.runcode reduce-method proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo