Skip to main content
VulnerabilityPublished Updated

CVE-2025-71339: Picklescan is vulnerable to RCE through missing detection when calling numpy.f2py.crackfortran._eval_length

Affects picklescanSource GCVE Database

0

Not known to be exploited · CVSS 8.1 High : upgrade to 0.0.33 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.0.33
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade picklescan to 0.0.33.

Affected software

ProductAffectedFixed in
PyPIpicklescanAffected
  • <0.0.33
Fixed in
  • 0.0.33

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid trusting Picklescan's results for untrusted pickle files, and consider alternative methods to validate or sandbox unpickling operations to prevent arbitrary code execution.

Description

Picklescan versions prior to 0.0.33 fail to detect malicious pickle files that exploit the numpy.f2py.crackfortran._eval_length function during unpickling. This allows attackers to execute arbitrary Python code when a crafted pickle is loaded, despite Picklescan reporting the file as safe. The vulnerability enables arbitrary code execution in workflows relying on Picklescan to vet untrusted pickle or PyTorch artifacts, potentially facilitating supply-chain poisoning of shared model files.

References

Community reviews

Loading reviews…