Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 21 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) < 0.0.30.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-21: Version 0.0.30 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run picklescan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a deserialization bypass (CWE-502) in picklescan's detection logic. The root cause is that picklescan fails to identify cProfile.runctx, a built-in Python profiling function that can execute arbitrary code, when it is called via the __reduce__ method in pickle serialization. An attacker constructs a malicious pickle file containing cProfile.runctx(cmd, globals, locals) in the reduce method, which effectively calls exec(cmd, ...) at deserialization time. The attack requires user interaction (victim must call pickle.load() on an untrusted file) but no privileges; it is exploitable over the network if the pickle file can be transmitted remotely. The vulnerability affects picklescan versions before 0.0.30, which includes a patch to detect this function call pattern.
Affected products
- mmaitre314 picklescan < 0.0.30
Timeline
- 2026-06-21: disclosed: Advisory published
- 2026-06-21: patched: Version 0.0.30 released with fix