Quick answers
- Is CVE-2025-71360 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71360 being exploited in the wild.
- How severe is CVE-2025-71360?
- High severity, with a CVSS score of 8.1, published 4 July 2026.
- Which products and versions are affected?
- picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.29.
- Is there a fix for CVE-2025-71360?
- Yes. picklescan (PyPI): upgrade to 0.0.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71360 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71360?
- 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.29 or later
pip install "picklescan>=0.0.29"
Technical details
A deserialization vulnerability (CWE-502) exists in picklescan due to an incomplete blocklist of dangerous functions. Specifically, the tool fails to identify the 'idlelib.calltip.get_entity' function when used within a pickle's '__reduce__' method. Because 'get_entity' internally performs an evaluation of its input, an attacker can craft a malicious pickle file that executes arbitrary Python code (e.g., os.system calls). The attack requires a victim to scan the file with an affected version of picklescan and, believing it to be safe, proceed to load it using 'pickle.load()'. This issue is resolved in version 0.0.29.
Affected products
- picklescan picklescan < 0.0.29
Identifiers
- CVE-2025-71360
- GHSA-9xph-j2h6-g47v
Timeline
- 2025-08-26: advisory: Initial GHSA advisory published
- 2026-07-04: disclosed: CVE-2025-71360 published to NVD