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.1, published 21 June 2026.

Is there a fix for This vulnerability?

A patch was published on 2026-06-21: Fix released in picklescan 0.0.30 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

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

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.

Picklescan missing detection for idlelib.pyshell.ModifiedInterpreter.runcommand

Severity: high · CVSS 8.1 · Published 2026-06-21

Picklescan is a security library used to validate pickle files before loading them—a critical safeguard in machine learning workflows where untrusted model files are common. This vulnerability allows attackers to craft pickle files containing hidden malicious code that passes Picklescan's safety checks but executes arbitrary commands when loaded. This is particularly dangerous in supply chain attacks targeting ML models, APIs, and saved Python objects.

Technologies: picklescan (PyPI). Vendors: PyPI.

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.1, published 21 June 2026.
Which products and versions are affected?: picklescan (PyPI) < 0.0.30.
Is there a fix for This vulnerability?: A patch was published on 2026-06-21: Fix released in picklescan 0.0.30 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
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

The vulnerability is a detection bypass in the deserialization safety checker (CWE-502). Picklescan fails to detect when a pickle file's reduce method calls idlelib.pyshell.ModifiedInterpreter.runcommand, a built-in Python function that can execute arbitrary code. An attacker constructs a malicious pickle object by overriding __reduce__ to invoke this function with a payload string (e.g., OS commands). When a victim uses Picklescan to validate the file and receives a clean verdict, they proceed to pickle.load() the file, triggering execution of the embedded payload. The attack requires user interaction (victim must load the pickle) but no authentication. Picklescan versions before 0.0.30 are affected; patching updates the detection rules to identify this gadget chain.

Affected products

mmaitre314 picklescan < 0.0.30

Timeline

2026-06-21: disclosed: Advisory published to GitHub Advisory Database
2026-06-21: patched: Fix released in picklescan 0.0.30

References

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