Code execution via omitted runctx blocklist entry
Published Jun 23, 2026 · Updated Jun 23, 2026
Security-control bypass in picklescan before 0.0.29 allows remote attackers to conceal code execution in a crafted pickle file. The scanner's unsafe-global blocklist omits profile.Profile.runctx, so a reduce tuple naming that callable passes analysis even though runctx executes an attacker-controlled Python string. Execution occurs only after a user or application trusts the scan result and deserializes the file, allowing the payload to read or write data with that process's privileges.
Summary
What happened
Security-control bypass in picklescan before 0.0.29 allows remote attackers to conceal code execution in a crafted pickle file. The scanner's unsafe-global blocklist omits profile.Profile.runctx, so a reduce tuple naming that callable passes analysis even though runctx executes an attacker-controlled Python string. Execution occurs only after a user or application trusts the scan result and deserializes the file, allowing the payload to read or write data with that process's privileges.
The record
- CVE
- CVE-2025-71341
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Matthieu Maitre
- Product
- picklescan
- Classifications
- CWE-502, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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.29
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
- GHSA-6vqj-c2q5-j97w profile.Profile.runctx 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