CVE-2025-71349 picklescan CVE debrief

Who should care

Defenders responsible for systems using picklescan, particularly those processing untrusted pickle files, should assess exposure and prioritize updating picklescan to version 0.0.29 or later.

Why it matters

CVE-2025-71349 allows attackers to embed undetected malicious code in pickle files due to a detection failure in picklescan before 0.0.29. Defenders should prioritize verifying and updating picklescan, restricting processing of untrusted pickle files, and monitoring for suspicious activity.

• Potential for arbitrary code execution when processing malicious pickle files
• Need for verification of picklescan version and inventory of affected systems
• Priority for updating picklescan to version 0.0.29 or later
• Possible impact on systems processing untrusted pickle files

Technical summary

The picklescan library before version 0.0.29 does not detect the built-in trace.Trace.run function when analyzing pickle files. This allows attackers to craft malicious pickle files that can execute arbitrary code when processed by pickle.load. The vulnerability enables attackers to embed undetected malicious code in pickle files, potentially leading to arbitrary code execution. Defenders should prioritize verifying and updating picklescan to version 0.0.29 or later, and restrict processing of untrusted pickle files.

Defensive priority

Defenders should prioritize verifying and updating picklescan to version 0.0.29 or later, and restrict processing of untrusted pickle files.

Recommended defensive actions

• Verify and update picklescan to version 0.0.29 or later
• Restrict processing of untrusted pickle files
• Monitor for suspicious pickle file activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in picklescan before 0.0.29. Limited information is available on affected versions and remediation beyond updating picklescan. Defenders should verify picklescan version and inventory affected systems, and monitor for suspicious pickle file activity. The detection failure in picklescan allows attackers to embed undetected malicious code in pickle files.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.