Quick answers
- Is CVE-2025-71359 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71359 being exploited in the wild.
- How severe is CVE-2025-71359?
- 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.29.
- Is there a fix for CVE-2025-71359?
- Yes. picklescan (PyPI): upgrade to 0.0.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71359 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71359?
- 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.29 or later
pip install "picklescan>=0.0.29"
Technical details
A deserialization vulnerability exists in picklescan due to an incomplete blocklist or detection logic. The tool fails to identify malicious payloads that wrap dangerous code within the 'lib2to3.pgen2.grammar.Grammar.loads' function during the pickle '__reduce__' process. An attacker can craft a malicious pickle file (often distributed as a machine learning model) that evades detection by picklescan. When a victim subsequently loads this file using 'pickle.load()', the embedded payload executes arbitrary code. This issue is resolved in version 0.0.29.
Affected products
- picklescan picklescan < 0.0.29
Identifiers
- CVE-2025-71359
- GHSA-f54q-57x4-jg88
Timeline
- 2025-08-26: advisory: GitHub Security Advisory published
- 2026-07-04: disclosed: NVD publication date
- 2026-07-04: patched: Fix confirmed in version 0.0.29