Is CVE-2025-71371 exploited in the wild?

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

How severe is CVE-2025-71371?

High severity, with a CVSS score of 8.1, published 30 June 2026.

Which products and versions are affected?

picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.29.

Is there a fix for CVE-2025-71371?

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

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

Am I affected by CVE-2025-71371?

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-71371: picklescan detection bypass via code.InteractiveInterpreter.runcode

CVE-2025-71371 · Severity: high · CVSS 8.1 · Published 2026-06-30

picklescan is a security tool used to scan Python pickle files and machine learning models (like PyTorch) for malicious code. A vulnerability in versions before 0.0.29 allows specially crafted malicious files to bypass detection by using a specific Python internal function. If a user relies on the tool's "safe" verdict and proceeds to open the file, an attacker could gain full control over the user's system.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71371 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71371 being exploited in the wild.
How severe is CVE-2025-71371?: High severity, with a CVSS score of 8.1, published 30 June 2026.
Which products and versions are affected?: picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.29.
Is there a fix for CVE-2025-71371?: 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-71371 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71371?: 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 of dangerous functions. Specifically, the tool fails to identify the use of 'code.InteractiveInterpreter.runcode' within a pickle's __reduce__ method. An attacker can craft a malicious pickle payload that picklescan flags as safe; however, when the victim subsequently loads the file using 'pickle.load()', the payload executes arbitrary Python code. This bypasses the primary security control intended for scanning untrusted machine learning models and serialized Python objects. The issue is resolved in version 0.0.29.

Affected products

picklescan picklescan < 0.0.29

Identifiers

CVE-2025-71371
GHSA-cj3c-v495-4xqh

Timeline

2025-08-26: advisory: Initial GitHub security advisory published
2026-06-30: disclosed: CVE-2025-71371 published and enriched by VulnCheck

References

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