CVE-2025-71349

Received Received - Intake

picklescan Arbitrary Code Execution via Unchecked trace.Trace.run

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-30

Last Modified

2026-06-30

Generated

2026-07-01

AI Q&A

2026-07-01

EPSS Evaluated

N/A

NVD

CVE-2025-71349

EUVD

EUVD-2025-210385

Affected Vendors & Products

Vendor	Product	Version / Range
picklescan	picklescan	to 0.0.29 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-502	The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

Executive Summary

The vulnerability exists in picklescan versions before 0.0.29, where the tool fails to detect the built-in trace.Trace.run function when analyzing pickle files.

This failure allows attackers to embed malicious code that goes undetected by picklescan.

Specifically, remote attackers can craft malicious pickle files that use trace.Trace.run in the reduce method, which leads to arbitrary code execution when the pickle.load function processes these files.

Impact Analysis

This vulnerability can lead to arbitrary code execution on systems that use vulnerable versions of picklescan to analyze pickle files.

An attacker can remotely craft malicious pickle files that, when loaded, execute unauthorized code, potentially compromising the affected system.

Hi! I’m here to help you understand CVE-2025-71349. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70