CVE-2025-71339

Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran._eval_length Gadget

Published Jun 22, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability arises because Picklescan fails to detect the numpy.f2py.crackfortran._eval_length gadget within pickle __reduce__ methods. As a result, an attacker can craft a malicious pickle file that will execute arbitrary Python code when the file is loaded by a user who trusts Picklescan’s safety validation. The weakness is defined as a vulnerability in the serialization mechanism (CWE‑502).

Affected Systems

The affected product is Picklescan. Versions prior to 0.0.33 are affected, including 0.0.32 and earlier. No other vendors or products are currently listed as impacted.

Risk and Exploitability

The CVSS score of 7.6 indicates high severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is local; the attacker needs to supply or influence the loading of a malicious pickle file, which typically requires social engineering or compromise of a trusted source. Exploitation can lead to full code execution on the victim’s machine. Given the high CVSS and the potential for local exploitation, organizations should treat this as a high‑risk issue.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Picklescan to version 0.0.33 or later to apply the vendor fix.
  • If an immediate update is not possible, configure Picklescan to reject any pickle files that contain the numpy.f2py.crackfortran._eval_length gadget by tightening its safety validation rules.
  • Limit the ingestion of pickle files to trusted, verified sources and avoid loading untrusted pickle data whenever possible.

Generated by OpenCVE AI on June 22, 2026 at 23:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6556-fwc2-fg2p Picklescan is vulnerable to RCE through missing detection when calling numpy.f2py.crackfortran._eval_length
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran._eval_length Gadget
First Time appeared Mmaitre314
Mmaitre314 picklescan
Weaknesses CWE-502
CPEs cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*
Vendors & Products Mmaitre314
Mmaitre314 picklescan
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jun 23, 2026, 3:06 PM
Reserved
Jun 20, 2026, 1:48 AM
Status
Deferred
Published
Jun 22, 2026, 10:16 PM
Modified
Oct 12, 2026, 10:10 PM