Description
picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.run.Executive.runcode in reduce methods. Attackers can embed undetected code in pickle files that executes during pickle.load, enabling remote code execution in PyTorch models and supply chain attacks.
Published: 2026-07-04
Score: 7.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

picklescan versions before 0.0.30 ignore malicious content in pickle payloads that use the standard library function idlelib.run.Executive.runcode during deserialization; the code runs automatically inside pickle.load, delivering arbitrary‑code execution whenever an attacker delivers a crafted file. This flaw, classified as CWE‑502, can be used to compromise systems handling PyTorch models or any other application that relies on picklescan for loading data.

Affected Systems

The product affected is the Python library picklescan, developed by mmaitre314. All releases earlier than 0.0.30 are vulnerable; later versions have not been identified as containing the issue.

Risk and Exploitability

The CVSS score of 7.6 signals a high‑severity weakness. An EPSS score below 1 % indicates that automated exploitation is currently uncommon, and the vulnerability is not listed in CISA’s KE attacker would need to supply a dangerous pickle file to an application that uses picklescan to deserialize data – the attack vector is therefore malicious file to reach the target; executes with the privileges of the picking process.

Generated by OpenCVE AI on July 21, 2026 at 08:58 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade picklescan to 0.0.30 or later to apply the vendor‑supplied fix.
  • Configure the application to validate and reject untrusted pickle files before they reach pickle.load, ensuring only known safe data is deserialized.
  • If an upgrade cannot be performed immediately, remove or neutralize the idlelib.run.Executive.runcode usage within picklescan’s reduce methods, or wrap the deserialization in a restricted sandbox environment.

Generated by OpenCVE AI on July 21, 2026 at 08:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 06 Jul 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 04 Jul 2026 03:45:00 +0000

Type Values Removed Values Added
First Time appeared Picklescan
Picklescan picklescan
Vendors & Products Picklescan
Picklescan picklescan

Sat, 04 Jul 2026 01:45:00 +0000

Type Values Removed Values Added
Description picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.run.Executive.runcode in reduce methods. Attackers can embed undetected code in pickle files that executes during pickle.load, enabling remote code execution in PyTorch models and supply chain attacks.
Title picklescan - Undetected Remote Code Execution via idlelib.run.Executive.runcode
First Time appeared Mmaitre314
Mmaitre314 picklescan
Weaknesses CWE-502
CPEs cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*
Vendors & Products Mmaitre314
Mmaitre314 picklescan
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Mmaitre314 Picklescan
Picklescan Picklescan
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-07-06T16:28:15.247Z

Reserved: 2026-06-20T12:48:06.735Z

Link: CVE-2025-71342

cve-icon Vulnrichment

Updated: 2026-07-06T16:28:10.576Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-21T09:00:03Z

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data