Is CVE-2025-71354 exploited in the wild?

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

How severe is CVE-2025-71354?

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

Which products and versions are affected?

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

Is there a fix for CVE-2025-71354?

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

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

Am I affected by CVE-2025-71354?

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-71354: picklescan detection bypass via idlelib.debugobj.ObjectTreeItem.SetText

Q: Which products and versions are affected?

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

Q: Is there a fix for CVE-2025-71354?

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.

Q: How is CVE-2025-71354 attacked?

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

Q: Am I affected by CVE-2025-71354?

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-71354 · Severity: high · CVSS 8.1 · Published 2026-06-24

Picklescan is a security tool used to detect malicious code hidden within Python "pickle" files, which are commonly used to store Machine Learning models like PyTorch. A vulnerability was found where certain specially crafted files could bypass these security checks by using a specific built-in Python function. If a user relies on Picklescan and then opens one of these undetected malicious files, an attacker could remotely execute code on their system, potentially leading to data theft or full system compromise.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71354 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71354 being exploited in the wild.
How severe is CVE-2025-71354?: High severity, with a CVSS score of 8.1, published 24 June 2026.
Which products and versions are affected?: picklescan (PyPI) < 0.0.29, ECOSYSTEM:introduced=0,fixed=0.0.29.
Is there a fix for CVE-2025-71354?: 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-71354 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71354?: 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

Picklescan versions prior to 0.0.29 contain a detection bypass vulnerability. The tool fails to identify malicious payloads that leverage the 'idlelib.debugobj.ObjectTreeItem.SetText' function within a pickle's __reduce__ method. An attacker can craft a malicious pickle file (such as a PyTorch model) that appears safe to Picklescan but executes arbitrary commands via the 'setfunction' parameter when loaded using 'pickle.load()'. This is a classic deserialization gadget bypass. The issue is resolved in version 0.0.29 by adding the missing function to the blocklist.

Affected products

mmaitre314 picklescan < 0.0.29

Identifiers

CVE-2025-71354
GHSA-3vg9-h568-4w9m
PYSEC-2026-1781

Timeline

2025-08-26: disclosed
2025-08-26: advisory
2025-08-26: patched: Fixed in version 0.0.29

References

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