Is CVE-2025-71358 exploited in the wild?

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

How severe is CVE-2025-71358?

High severity, with a CVSS score of 8.1, published 22 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-71358?

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

It is attacked with local access, in a software library.

Am I affected by CVE-2025-71358?

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-71358: picklescan detection bypass via idlelib get_entity function

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

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

It is attacked with local access, in a software library.

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

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

Picklescan is a security tool used to detect malicious code hidden in Python "pickle" files, which are commonly used to store machine learning models. A vulnerability was found where certain malicious commands could bypass detection by using a specific Python library function. If a user relies on Picklescan to verify a file and then opens it, an attacker could execute arbitrary code on the user's system.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71358 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71358 being exploited in the wild.
How severe is CVE-2025-71358?: High severity, with a CVSS score of 8.1, published 22 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-71358?: 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-71358 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2025-71358?: 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) contains a detection bypass vulnerability. The tool fails to flag malicious pickle files that use the `idlelib.autocomplete.AutoComplete.get_entity` function within a `__reduce__` method to execute arbitrary system commands. An attacker can craft a malicious pickle file (such as a PyTorch model) that passes Picklescan's security checks but executes code via `pickle.load()`. This is a bypass of the library's primary security function. The issue is resolved in version 0.0.29.

Affected products

mmaitre314 picklescan < 0.0.29

Identifiers

CVE-2025-71358
GHSA-6w4w-5w54-rjvr
PYSEC-2026-1784

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.