CVE-2025-71349

picklescan - Arbitrary Code Execution via Undetected trace.Trace.run in Pickle Files

Published Jun 30, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
picklescan before 0.0.29 fails to detect the built-in trace.Trace.run function when analyzing pickle files, allowing attackers to embed undetected malicious code. Remote attackers can craft malicious pickle files using trace.Trace.run in the reduce method to achieve arbitrary code execution when pickle.load processes the file.

Analysis

AI-generated

Technical impact

picklescan versions prior to 0.0.29 fail to strip out the built‑in trace.Trace.run command when analyzing pickle files, allowing an attacker to embed malicious code inside a pickle payload. When pickle.load processes such a file, the injected code is executed, resulting in control over the host system. This flaw is a classic deserialization vulnerability (CWE-502).

Affected Systems

Users of picklescan:picklescan installation earlier than 0.0.29 are impacted; any environment that imports or loads untrusted pickle objects rendered by that version can be compromised.

Risk and Exploitability

The CVSS score of 7.6 indicates a moderate to high risk of exploitation, but the EPSS score is not available, limiting visibility into current attack likelihood. The vulnerability is not listed in the CISA KEV catalog, so no known large‑scale exploitation has been reported in the public feeds. The attack likely requires an attacker to supply a malicious pickle file to a system that processes it with picklescan; based on the description, the vector is remote or local depending on how the application accepts pickle data, so caution is advised for any service that ingests external pickles.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade picklescan to 0.0.29 or later to remove the trace.Trace.run processing flaw
  • If an upgrade is not immediately possible, restrict picklescan usage to strictly trusted pickle payloads and block or sanitize all external files
  • Implement input validation that detects the trace.Trace.run pattern and rejects or safely handles such payloads before they reach pickle.load

Generated by OpenCVE AI on June 30, 2026 at 23:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description picklescan before 0.0.29 fails to detect the built-in trace.Trace.run function when analyzing pickle files, allowing attackers to embed undetected malicious code. Remote attackers can craft malicious pickle files using trace.Trace.run in the reduce method to achieve arbitrary code execution when pickle.load processes the file.
Title picklescan - Arbitrary Code Execution via Undetected trace.Trace.run in Pickle Files
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'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jul 1, 2026, 2:05 PM
Reserved
Jun 20, 2026, 12:48 PM
Status
Deferred
Published
Jun 30, 2026, 11:16 PM
Modified
Oct 12, 2026, 9:10 PM