CVE-2025-71339
Received Received - Intake
Picklescan Arbitrary Code Execution via Unsafe Pickle Deserialization

Publication date: 2026-06-22

Last updated on: 2026-06-22

Assigner: VulnCheck

Description
Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran._eval_length gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded by victims who trust Picklescan's safety validation.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-22
Last Modified
2026-06-22
Generated
2026-06-23
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Picklescan versions before 0.0.33, where the software fails to detect a specific gadget called numpy.f2py.crackfortran._eval_length within pickle __reduce__ methods.

Because of this failure, attackers can create malicious pickle files that execute arbitrary Python code when these files are loaded by users who rely on Picklescan's safety validation.

Impact Analysis

The vulnerability allows attackers to execute arbitrary Python code on a victim's system by tricking them into loading a malicious pickle file that bypasses Picklescan's safety checks.

This can lead to unauthorized actions, potential system compromise, data manipulation, or other malicious activities depending on the attacker's intent.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-71339. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart