Quick answers
- Is CVE-2025-71323 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-71323 being exploited in the wild.
- How severe is CVE-2025-71323?
- Critical severity, with a CVSS score of 9.8, published 17 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) < 0.0.33, ECOSYSTEM:introduced=0,fixed=0.0.33.
- Is there a fix for CVE-2025-71323?
- 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-71323 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-71323?
- 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 vulnerability exists in picklescan versions prior to 0.0.33 due to an incomplete list of disallowed inputs (CWE-184). The scanner fails to flag the 'ctypes' module, which provides foreign function interface capabilities. An attacker can exploit this by crafting a malicious pickle file that uses ctypes.WinDLL to load system libraries (like kernel32.dll) and execute arbitrary commands. This bypasses the tool's sandbox protections and gadget chain detection by utilizing direct syscalls and raw memory access. The issue is resolved in version 0.0.33.
Affected products
- picklescan picklescan < 0.0.33
Identifiers
- CVE-2025-71323
- GHSA-4675-36f9-wf6r
- PYSEC-2026-1782
Timeline
- 2025-12-26: advisory: GitHub Security Advisory published
- 2026-06-17: disclosed: NVD publication date