Is CVE-2025-71367 exploited in the wild?

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

How severe is CVE-2025-71367?

High severity, with a CVSS score of 8.1, published 4 July 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2025-71367?

Yes. picklescan (PyPI): upgrade to 0.0.34 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-71367 attacked?

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

Am I affected by CVE-2025-71367?

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-71367: picklescan security bypass via _operator.attrgetter function call

CVE-2025-71367 · Severity: high · CVSS 8.1 · Published 2026-07-04

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 function. If a user relies on picklescan to verify a file and then opens it, an attacker could execute arbitrary commands on the user's system.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71367 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71367 being exploited in the wild.
How severe is CVE-2025-71367?: High severity, with a CVSS score of 8.1, published 4 July 2026.
Which products and versions are affected?: picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.34.
Is there a fix for CVE-2025-71367?: Yes. picklescan (PyPI): upgrade to 0.0.34 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-71367 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71367?: 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.34 or later
```
pip install "picklescan>=0.0.34"
```

Technical details

A deserialization vulnerability (CWE-502) exists in picklescan due to an incomplete denylist of dangerous functions. Specifically, the tool fails to identify and flag the '_operator.attrgetter' function when used within a pickle's reduce method. An attacker can craft a malicious pickle file that uses this function to trigger arbitrary code execution upon loading. While picklescan is intended to prevent such attacks by pre-scanning files, this bypass allows malicious payloads to be marked as safe. The issue is resolved in version 0.0.34.

Affected products

picklescan picklescan < 0.0.34

Identifiers

CVE-2025-71367
GHSA-46h3-79wf-xr6c

Timeline

2025-12-27: advisory: GitHub Security Advisory published
2026-07-04: disclosed: NVD publication date

References

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