CVE-2025-71349 picklescan - Arbitrary Code Execution via Undetected trace.Trace.run in Pickle Files
Attackers can achieve arbitrary code execution by crafting malicious pickle files that bypass picklescan's detection of trace.Trace.run.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-71349?
CVE-2025-71349 is a high-severity unsafe deserialization vulnerability in picklescan, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-502
Which versions are affected by CVE-2025-71349?
2 open source packages ship an affected version, including picklescan.
| Package | Affected | Fixed in |
|---|---|---|
picklescan PyPI | All versions | 0.0.29 |
picklescan PyPI | All versions | 0.0.29 |
How do I fix CVE-2025-71349?
Upgrade picklescan to 0.0.29 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-71349 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71349 exists.
Sources
Also known as GHSA-3cjr-683m-5fxh, GHSA-5qwp-399c-mjwf.