CVE-2025-71347 picklescan CVE debrief

Who should care

Developers and users of picklescan, especially those using versions before 0.0.33, should be aware of this vulnerability. Applications that load untrusted pickle data are at risk of arbitrary code execution. Users should prioritize updating picklescan to version 0.0.33 or later to mitigate this vulnerability.

Technical summary

The vulnerability in picklescan before 0.0.33 stems from its inability to detect malicious pickle files that utilize the numpy.f2py.crackfortran.param_eval function in reduce methods. This oversight allows attackers to craft pickle files that, when deserialized, execute arbitrary code. The issue is particularly concerning for applications that deserialize untrusted pickle data, as it could lead to remote code execution. The Common Weakness Enumeration (CWE) associated with this vulnerability is CWE-502.

Defensive priority

High priority should be given to updating picklescan to version 0.0.33 or later. In the meantime, defenders should treat pickle files from untrusted sources with extreme caution and consider implementing additional security measures to detect and prevent the loading of malicious pickle files.

Recommended defensive actions

• Update picklescan to version 0.0.33 or later.
• Treat pickle files from untrusted sources with extreme caution.
• Implement additional security measures to detect and prevent the loading of malicious pickle files.
• Monitor applications that deserialize pickle data for suspicious activity.
• Consider using alternative serialization formats that are safer than pickle.

Evidence notes

The evidence for this CVE comes from the NVD and Vulncheck. The CVE was published on 2026-07-04T02:16:21.803Z and has not been modified since then. The vulnerability details were obtained from the CVE record and the Vulncheck advisory.

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.