Quick answers
- Is CVE-2025-71369 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71369 being exploited in the wild.
- How severe is CVE-2025-71369?
- 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-71369?
- 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-71369 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71369?
- 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 scanner fails to identify the use of 'torch.utils.data.datapipes.utils.decoder.basichandlers' within a pickle object's '__reduce__' method. An attacker can wrap a secondary malicious payload within this PyTorch handler, which picklescan ignores during its safety audit. When a victim subsequently loads the 'verified' file using 'pickle.load()', the handler executes the embedded payload. This bypass enables remote code execution (RCE) on the host machine. The issue is resolved in version 0.0.28.
Affected products
- picklescan picklescan < 0.0.28
Identifiers
- CVE-2025-71369
- GHSA-h3qp-7fh3-f8h4
Timeline
- 2025-08-22: advisory: Initial GitHub security advisory published
- 2026-07-04: disclosed: NVD publication date