Quick answers
- Is CVE-2025-71320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71320 being exploited in the wild.
- How severe is CVE-2025-71320?
- Critical severity, with a CVSS score of 9.8, published 17 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) < 0.0.33, ECOSYSTEM:introduced=0,fixed=0.0.33.
- Is there a fix for CVE-2025-71320?
- Yes. picklescan (PyPI): upgrade to 0.0.33 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71320 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71320?
- 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.33 or later
pip install "picklescan>=0.0.33"
Technical details
picklescan versions prior to 0.0.33 suffer from an incomplete list of disallowed inputs (CWE-184) within its security scanning logic. The tool fails to block the 'pydoc.locate' and 'operator.methodcaller' functions, which can be leveraged to dynamically resolve modules and execute arbitrary methods. An attacker can exploit this by crafting a malicious pickle file that uses these functions to bypass the scanner's "Dangerous" classification. When the resulting file is deserialized by a victim, it leads to arbitrary code execution. This vulnerability is addressed in version 0.0.33 by expanding the deny-list to block these modules entirely.
Affected products
- picklescan picklescan < 0.0.33
Identifiers
- CVE-2025-71320
- GHSA-84r2-jw7c-4r5q
- PYSEC-2026-1785
Timeline
- 2025-12-26: advisory: GitHub Security Advisory published
- 2026-06-17: disclosed: NVD publication and CVE assignment