CVE-2025-71339: Picklescan is vulnerable to RCE through missing detection when calling numpy.f2py.crackfortran._eval_length
Affects picklescanSource GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 0.0.33 soon.
Data as of 26 Oct 2026, 10:12 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PyPIpicklescan | Affected
| Fixed in
|
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
- github.com/mmaitre314/picklescan/security/advisories/GHSA-6556-fwc2-fg2p (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-71339 (opens in a new tab)
- github.com/mmaitre314/picklescan/pull/53 (opens in a new tab)
- github.com/mmaitre314/picklescan/commit/70c1c6c31beb6baaf52c8db1b6c3c0e84a6f9dab (opens in a new tab)
- github.com/advisories/GHSA-6556-fwc2-fg2p (opens in a new tab)
- github.com/mmaitre314/picklescan (opens in a new tab)
- github.com/mmaitre314/picklescan/releases/tag/v0.0.33 (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/picklescan/PYSEC-2026-1783.yaml (opens in a new tab)
- pypi.org/project/picklescan (opens in a new tab)
- vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-numpy-f2py-crackfortran-eval-length-gadget (opens in a new tab)