Is CVE-2025-71374 exploited in the wild?

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

How severe is CVE-2025-71374?

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

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

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

Am I affected by CVE-2025-71374?

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-71374: picklescan detection bypass via profile.Profile.run

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

picklescan is a security tool used to scan Python pickle files and machine learning models for malicious code. A flaw in the tool allows specially crafted files to bypass its security checks by using a specific Python profiling function. If a user trusts the tool's clean scan result and opens the malicious file, an attacker could gain full control over the user's system.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71374 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71374 being exploited in the wild.
How severe is CVE-2025-71374?: 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-71374?: 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-71374 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71374?: 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 'profile.Profile.run' function when it is invoked within a pickle's '__reduce__' method. An attacker can exploit this by crafting a malicious pickle file (often disguised as a PyTorch model) that bypasses detection. When a victim subsequently loads the file using 'pickle.load()', the embedded payload executes arbitrary system commands. This issue is addressed in version 0.0.29.

Affected products

picklescan picklescan < 0.0.29

Identifiers

CVE-2025-71374
GHSA-x696-vm39-cp64

Timeline

2025-08-26: advisory: GHSA-x696-vm39-cp64 published
2026-06-30: disclosed: CVE-2025-71374 published to NVD

References

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