Code execution via runcommand blocklist omission
Published Jun 21, 2026 · Updated Jun 21, 2026
Protection bypass in picklescan before 0.0.30 allows remote attackers to execute commands through a malicious pickle file. The scanner's _unsafe_globals blocklist omits idlelib.pyshell.ModifiedInterpreter.runcommand, so a reduce reference to that callable is reported as safe. Execution requires a recipient to trust the scan result and deserialize the file, after which the embedded command runs with that process's privileges.
Summary
What happened
Protection bypass in picklescan before 0.0.30 allows remote attackers to execute commands through a malicious pickle file. The scanner's _unsafe_globals blocklist omits idlelib.pyshell.ModifiedInterpreter.runcommand, so a reduce reference to that callable is reported as safe. Execution requires a recipient to trust the scan result and deserialize the file, after which the embedded command runs with that process's privileges.
The record
- CVE
- CVE-2025-71357
- Published
- Jun 21, 2026
- Updated
- Jun 21, 2026
- Vendor
- Matthieu Maitre
- Product
- picklescan
- Classifications
- CWE-502, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2026CVE publishedPublication date reported by the CVE source.
- Jun 21, 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.
Public exploit references
- GHSA-j343-8v2j-ff7w 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