Quick answers
- Is CVE-2025-71350 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71350 being exploited in the wild.
- How severe is CVE-2025-71350?
- High severity, with a CVSS score of 8.1, published 30 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.28.
- Is there a fix for CVE-2025-71350?
- 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-71350 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71350?
- 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 flag the 'torch.utils.collect_env.run' function when used within a pickle's __reduce__ method. An attacker can craft a malicious pickle file that executes arbitrary shell commands via this PyTorch utility. Because picklescan reports the file as safe, users are likely to proceed with pickle.load(), triggering the payload. The issue is resolved in version 0.0.28, which adds the missing function to the detection engine.
Affected products
- picklescan picklescan < 0.0.28
Identifiers
- CVE-2025-71350
- GHSA-f745-w6jp-hpxx
Timeline
- 2025-08-22: advisory: Initial GHSA advisory published
- 2026-06-30: disclosed: CVE-2025-71350 published to NVD