Quick answers
- Is CVE-2025-71355 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71355 being exploited in the wild.
- How severe is CVE-2025-71355?
- Medium severity, with a CVSS score of 4, published 30 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.25.
- Is there a fix for CVE-2025-71355?
- Yes. picklescan (PyPI): upgrade to 0.0.25 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71355 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71355?
- 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.
How to fix
- picklescan (PyPI): upgrade to 0.0.25 or later
pip install "picklescan>=0.0.25"
Technical details
Picklescan (versions prior to 0.0.25) contains an incomplete list of disallowed inputs (CWE-184) in its safety blacklist. Specifically, it fails to flag the 'numpy.testing._private.utils.runstring' function, which can be used within a pickle's __reduce__ method to execute arbitrary Python code. An attacker can craft a malicious pickle file that imports the 'os' library via this Numpy function to execute shell commands. The vulnerability is exploited when a victim scans a malicious file, receives a 'clean' report due to the bypass, and subsequently loads the file using 'pickle.load()'. The issue is resolved in version 0.0.25 by adding Numpy to the unsafe globals list.
Affected products
- mmaitre314 picklescan < 0.0.25
Identifiers
- CVE-2025-71355
- GHSA-fj43-3qmq-673f
Timeline
- 2025-04-06: advisory: GitHub Security Advisory published
- 2026-06-30: disclosed: NVD publication date