Quick answers
- Is CVE-2025-71370 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71370 being exploited in the wild.
- How severe is CVE-2025-71370?
- High severity, with a CVSS score of 8.1, published 23 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) <= 0.0.27, ECOSYSTEM:introduced=0,fixed=0.0.28.
- Is there a fix for CVE-2025-71370?
- Yes. picklescan (PyPI): upgrade to 0.0.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71370 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71370?
- 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.28 or later
pip install "picklescan>=0.0.28"
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 'torch.jit.unsupported_tensor_ops.execWrapper' function when embedded in pickle files. An attacker can craft a malicious pickle file using this function to execute arbitrary Python code. If a victim scans the file with an affected version of picklescan and subsequently loads it using 'pickle.load()', the payload will execute. This bypasses the primary security guarantee of the library. The issue is resolved in version 0.0.28.
Affected products
- mmaitre314 picklescan < 0.0.28
Identifiers
- CVE-2025-71370
- GHSA-vr7h-p6mm-wpmh
- PYSEC-2026-4136
Timeline
- 2025-08-22: advisory: Initial GitHub security advisory published
- 2026-06-23: disclosed: CVE-2025-71370 published to NVD