Quick answers
- Is CVE-2025-71372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71372 being exploited in the wild.
- How severe is CVE-2025-71372?
- 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-71372?
- 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-71372 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71372?
- 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 is vulnerable to a deserialization bypass (CWE-502) because its blocklist/heuristic engine fails to identify the 'numpy.f2py.crackfortran.getlincoef' function as a dangerous gadget. An attacker can craft a malicious pickle file that utilizes this function within a '__reduce__' method to execute arbitrary Python code. When a victim scans the file, Picklescan incorrectly flags it as safe; subsequent loading of the file via 'pickle.load()' triggers the exploit. This vulnerability requires the victim to attempt to load the malicious file (User Interaction) and is resolved in version 0.0.33.
Affected products
- Picklescan Picklescan before 0.0.33
Identifiers
- CVE-2025-71372
- GHSA-rrxm-2pvv-m66x
Timeline
- 2025-12-27: advisory: GitHub Security Advisory published
- 2026-07-03: disclosed: NVD publication date
- 2026-07-03: patched: Version 0.0.33 released