Quick answers
- Is CVE-2025-71366 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71366 being exploited in the wild.
- How severe is CVE-2025-71366?
- 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.28.
- Is there a fix for CVE-2025-71366?
- 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-71366 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71366?
- 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 versions prior to 0.0.28. The scanner's blocklist/allowlist logic fails to identify the 'torch.utils.bottleneck.__main__.run_cprofile' function as a dangerous global. An attacker can craft a malicious pickle file using this function in a '__reduce__' method to execute arbitrary Python code. When a victim scans the file, picklescan reports it as safe; subsequent loading of the file via 'pickle.load()' results in arbitrary code execution. This issue is resolved in version 0.0.28.
Affected products
- picklescan picklescan < 0.0.28
Identifiers
- CVE-2025-71366
- GHSA-4r9r-ch6f-vxmx
Timeline
- 2025-08-22: advisory: GitHub Security Advisory published
- 2026-07-03: disclosed: CVE published to NVD