Arbitrary code execution via profile.run blocklist mismatch
Published Jun 17, 2026 · Updated Jun 17, 2026
Blocklist bypass in picklescan before 1.0.4 allows attackers to conceal arbitrary Python code execution in a malicious pickle file. In scanner.py, the profile blocklist compares the parsed global name run against Profile.run, so module-level profile.run passes as clean despite invoking exec(). Exploitation requires the crafted file to pass picklescan and then reach a pickle loader, where attacker-supplied Python runs with the loader process's privileges.
Summary
What happened
Blocklist bypass in picklescan before 1.0.4 allows attackers to conceal arbitrary Python code execution in a malicious pickle file. In scanner.py, the profile blocklist compares the parsed global name run against Profile.run, so module-level profile.run passes as clean despite invoking exec(). Exploitation requires the crafted file to pass picklescan and then reach a pickle loader, where attacker-supplied Python runs with the loader process's privileges.
The record
- CVE
- CVE-2026-53873
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Matthieu Maitre
- Product
- picklescan
- Classifications
- CWE-697, CWE-184, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 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 <1.0.4
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
- profile.run malicious pickle 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