Quick answers
- Is CVE-2025-71373 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71373 being exploited in the wild.
- How severe is CVE-2025-71373?
- 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.33.
- Is there a fix for CVE-2025-71373?
- Yes. picklescan (PyPI): upgrade to 0.0.33 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-71373 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71373?
- 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.33 or later
pip install "picklescan>=0.0.33"
Technical details
A protection mechanism failure (CWE-693) exists in picklescan versions prior to 0.0.33. The library's scanning logic fails to identify and flag the 'operator.methodcaller' built-in Python function when embedded in pickle opcodes. An attacker can exploit this by manually crafting a malicious pickle payload that uses this function to trigger arbitrary system commands. Because picklescan reports the file as safe, downstream applications that rely on it for validation will proceed to load the file using 'pickle.load()', resulting in remote code execution. The vulnerability is particularly relevant for environments processing untrusted machine learning models or serialized Python objects.
Affected products
- picklescan picklescan < 0.0.33
Identifiers
- CVE-2025-71373
- GHSA-x843-g5mx-g377
Timeline
- 2025-12-27: advisory: GitHub Security Advisory published
- 2026-07-04: disclosed: NVD publication date