Is CVE-2025-71349 exploited in the wild?

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

How severe is CVE-2025-71349?

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

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

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

Am I affected by CVE-2025-71349?

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-71349: picklescan detection bypass via trace.Trace.run function

CVE-2025-71349 · 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 vulnerability exists where the tool fails to detect dangerous commands hidden within the 'trace.Trace.run' function. If a user relies on this tool to verify a file and then opens a malicious one, an attacker could gain full control over the user's system.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71349 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71349 being exploited in the wild.
How severe is CVE-2025-71349?: 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-71349?: 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-71349 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71349?: 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 versions prior to 0.0.29 due to an incomplete blocklist of dangerous functions. The tool fails to identify the 'trace.Trace.run' built-in Python function when it is embedded within a pickle file's '__reduce__' method. An attacker can exploit this by crafting a malicious pickle file that, when scanned, appears safe but executes arbitrary system commands upon subsequent loading via 'pickle.load()'. This bypasses the primary security utility of the library, which is often used to screen PyTorch models and other serialized Python objects. The issue is resolved in version 0.0.29.

Affected products

picklescan picklescan < 0.0.29

Identifiers

CVE-2025-71349
GHSA-5qwp-399c-mjwf

Timeline

2025-08-26: advisory: GitHub Security Advisory published
2026-06-30: disclosed: NVD publication date

References

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