Quick answers
- Is CVE-2025-71345 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71345 being exploited in the wild.
- How severe is CVE-2025-71345?
- 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.30.
- Is there a fix for CVE-2025-71345?
- Yes. picklescan (PyPI): upgrade to 0.0.30 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71345 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71345?
- 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.30 or later
pip install "picklescan>=0.0.30"
Technical details
A deserialization vulnerability (CWE-502) exists in picklescan versions prior to 0.0.30. The tool's blocklist/allowlist mechanism fails to account for the 'torch.utils.bottleneck.__main__.run_autograd_prof' function, which can be leveraged to execute arbitrary Python code during the unpickling process. An attacker can craft a malicious pickle file that bypasses picklescan's detection; when a victim subsequently loads this file using 'pickle.load()', the embedded payload executes. This enables remote code execution (RCE) with the privileges of the application loading the model. The issue is resolved in version 0.0.30.
Affected products
- picklescan picklescan < 0.0.30
Identifiers
- CVE-2025-71345
- GHSA-4whj-rm5r-c2v8
Timeline
- 2025-08-26: advisory: Initial GitHub security advisory published
- 2026-07-03: disclosed: CVE-2025-71345 published to NVD