CVE-2025-71374 picklescan CVE debrief

Who should care

Defenders handling untrusted pickle data, especially in Python environments using picklescan for security checks, should assess exposure and verify the presence of the fixed version.

Why it matters

CVE-2025-71374 is a high-severity vulnerability in picklescan that allows attackers to execute arbitrary code by bypassing detection of malicious pickle files. Defenders handling untrusted pickle data should verify the presence of picklescan version 0.0.29 or later and restrict deserialization of untrusted data.

• Code execution upon deserialization of malicious pickle files
• Bypass of picklescan detection for profile.Profile.run function
• Potential for arbitrary code execution in vulnerable systems

Technical summary

The picklescan library before version 0.0.29 fails to detect the built-in Python profile.Profile.run function when used in pickle reduce methods. This allows attackers to craft malicious pickle files that bypass picklescan detection and achieve code execution upon deserialization. The vulnerability affects systems using picklescan for security checks, particularly those handling untrusted pickle data. Defenders should prioritize verifying the presence of picklescan version 0.0.29 or later in their Python environments, especially in systems handling untrusted pickle data, to mitigate potential code execution risks.

Defensive priority

Defenders should prioritize verifying the presence of picklescan version 0.0.29 or later in their Python environments, especially in systems handling untrusted pickle data.

Recommended defensive actions

• Verify the version of picklescan is 0.0.29 or later
• Restrict the deserialization of untrusted pickle data
• 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, but the scope of affected systems and versions requires further verification. The picklescan library's failure to detect the profile.Profile.run function in pickle reduce methods allows for potential code execution. Defenders should verify the presence of picklescan version 0.0.29 or later and restrict deserialization of untrusted data. Evidence from the CVE record and NVD entry suggests that the vulnerability is high-severity, but additional verification is needed to确

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.