Quick answers
- Is CVE-2025-71375 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71375 being exploited in the wild.
- How severe is CVE-2025-71375?
- 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.34.
- Is there a fix for CVE-2025-71375?
- Yes. picklescan (PyPI): upgrade to 0.0.34 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71375 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71375?
- 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.34 or later
pip install "picklescan>=0.0.34"
Technical details
A deserialization vulnerability (CWE-502) exists in picklescan versions prior to 0.0.34 due to an incomplete blocklist of dangerous Python built-ins. Specifically, the scanner fails to detect the '_operator.methodcaller' function when it is used within a pickle payload's __reduce__ method. An attacker can craft a malicious pickle file that evades detection by picklescan but executes arbitrary system commands when subsequently loaded by 'pickle.load()'. Exploitation requires the victim to scan the malicious file and then proceed to deserialize it. The issue is resolved in version 0.0.34.
Affected products
- picklescan picklescan < 0.0.34
Identifiers
- CVE-2025-71375
- GHSA-955r-x9j8-7rhh
Timeline
- 2025-12-27: advisory: GitHub Security Advisory published
- 2026-07-04: disclosed: NVD publication date