CVE-2025-71349highCWE-502

CVE-2025-71349: high-severity vulnerability in picklescan

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

Published · Updated

Follow this CVE+ Monitor picklescan+ Monitor picklescan

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.6epss 0.6%
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:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
picklescan · picklescan
Related CVEs — picklescan

In the same product, most dangerous first.

CVE-2026-56315CRITICALpicklescan - Remote Code Execution via Unblocked Standard Library ModulesEPSS 1.1%CVE-2025-71323CRITICALpicklescan - Remote Code Execution via Unblocked ctypes ModuleEPSS 1.0%CVE-2025-71368HIGHpicklescan - Arbitrary Code Execution via Undetected doctest.debug_scriptEPSS 0.8%CVE-2025-71321CRITICALpicklescan - Arbitrary File Writing via distutils Module BypassEPSS 0.8%CVE-2026-3490CRITICALpicklescan - Universal Blocklist Bypass via pkgutil.resolve_nameEPSS 0.8%CVE-2025-71320CRITICALpicklescan - Remote Code Execution via Incomplete Disallowed InputsEPSS 0.8%