Is CVE-2025-71347 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-71347 being exploited in the wild.

How severe is CVE-2025-71347?

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-71347?

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-71347 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-71347?

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.

CVE-2025-71347: picklescan security bypass via numpy.f2py.crackfortran.param_eval

CVE-2025-71347 · Severity: high · CVSS 8.1 · Published 2026-07-04

picklescan is a security tool used to scan Python pickle files and machine learning models for malicious code. A vulnerability in versions before 0.0.33 allows specially crafted malicious files to bypass detection by using a specific NumPy function. If a user relies on the tool to verify a file and then opens it, an attacker could gain full control over the system running the code.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71347 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71347 being exploited in the wild.
How severe is CVE-2025-71347?: 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-71347?: 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-71347 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71347?: 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

A security bypass exists in picklescan versions prior to 0.0.33 due to an incomplete blocklist of dangerous functions. Specifically, the tool fails to identify the 'numpy.f2py.crackfortran.param_eval' function when used within a pickle's __reduce__ method. An attacker can craft a malicious pickle file that executes arbitrary Python code (e.g., via os.system) during deserialization. Because picklescan reports the file as safe, users are likely to proceed with loading the untrusted data using pickle.load(), resulting in remote code execution. The issue is addressed in version 0.0.33.

Affected products

picklescan picklescan < 0.0.33

Identifiers

CVE-2025-71347
GHSA-cffc-mxrf-mhh4

Timeline

2025-12-27: advisory: GitHub Security Advisory published
2026-07-04: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.