Is CVE-2025-71363 exploited in the wild?

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

How severe is CVE-2025-71363?

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.30.

Is there a fix for CVE-2025-71363?

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

How is CVE-2025-71363 attacked?

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

Am I affected by CVE-2025-71363?

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-71363: picklescan code execution bypass via cProfile.run in pickle reduce

CVE-2025-71363 · 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 'cProfile.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-71363 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-71363 being exploited in the wild.
How severe is CVE-2025-71363?: 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.30.
Is there a fix for CVE-2025-71363?: Yes. picklescan (PyPI): upgrade to 0.0.30 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-71363 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-71363?: 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.30 or later
```
pip install "picklescan>=0.0.30"
```

Technical details

A deserialization vulnerability (CWE-502) exists in picklescan versions prior to 0.0.30. The tool's detection logic fails to identify the 'cProfile.run' built-in function when used within a pickle object's '__reduce__' method. An attacker can craft a malicious pickle file that uses 'cProfile.run' to execute arbitrary Python statements (which internally calls 'exec'). Because picklescan marks these files as safe, users may proceed to load them using 'pickle.load()', resulting in remote code execution. The issue is resolved in version 0.0.30.

Affected products

picklescan picklescan < 0.0.30

Identifiers

CVE-2025-71363
GHSA-49gj-c84q-6qm9

Timeline

2025-08-26: advisory: Initial GitHub security advisory published
2026-06-30: disclosed: CVE published and NVD record created

References

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