Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.8, published 17 June 2026.
- Which products and versions are affected?
- picklescan (PyPI) < 0.0.33.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- 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.
Technical details
PickleScan before version 0.0.33 contains a protection mechanism failure (CWE-693) due to an incomplete 'unsafe globals' blocklist. Specifically, the 'pty.spawn' function was not categorized as dangerous, allowing it to be executed during the unpickling process if a user scans a malicious file. An attacker can exploit this by crafting a pickle payload (often embedded in PyTorch models or ZIP archives) that uses pty.spawn to execute arbitrary shell commands. The vulnerability is triggered when PickleScan processes the malicious file, leading to arbitrary code execution (ACE) with the privileges of the user running the scanner. The issue is resolved in version 0.0.33 by adding 'pty' to the internal _unsafe_globals list.
Affected products
- mmaitre314 picklescan < 0.0.33
Timeline
- 2025-12-26: advisory: Original GHSA-hgrh-qx5j-jfwx published
- 2026-06-17: disclosed: CVE-2025-71322 published
- 2026-06-18: other: Duplicate advisory GHSA-5gp7-4733-2w2v withdrawn