Quick answers
- Is CVE-2025-71362 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71362 being exploited in the wild.
- How severe is CVE-2025-71362?
- 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.33.
- Is there a fix for CVE-2025-71362?
- Yes. picklescan (PyPI): upgrade to 0.0.33 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71362 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71362?
- 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.33 or later
pip install "picklescan>=0.0.33"
Technical details
picklescan versions prior to 0.0.33 contain a detection bypass vulnerability (CWE-502) related to unsafe deserialization. The tool fails to identify malicious payloads that leverage functions within the `numpy.f2py.crackfortran` module, such as `getlincoef` and `_eval_length`, which internally call `eval()` on input strings. An attacker can craft a malicious pickle file that uses these NumPy functions as a gadget to execute arbitrary Python code. While the attack requires a user to attempt to load the malicious file, the failure of picklescan to flag the threat provides a false sense of security. The issue is resolved in version 0.0.33.
Affected products
- mmaitre314 picklescan < 0.0.33
Identifiers
- CVE-2025-71362
- GHSA-r8g5-cgf2-4m4m
Timeline
- 2025-12-26: advisory: Initial GitHub security advisory published
- 2026-07-04: disclosed: NVD publication date