Unsafe Deserialization in picklescan (CVE-2025-71339)
Summary
Vulnerability in picklescan (CVE-2025-71339). Confidential information can be exposed externally. Exploitable via numpy.f2py.crackfortran._eval_length. Mitigation: upgrade to 0.0.33 or later.
Original description
The description as published by the source.
Summary
Picklescan uses the numpy.f2py.crackfortran._eval_length function (a NumPy F2PY helper) to execute arbitrary Python code during unpickling.
Details
Picklescan fails to detect a malicious pickle that uses the gadget numpy.f2py.crackfortran._eval_length in __reduce__, allowing arbitrary command execution when the pickle is loaded. A crafted object returns this function plus attacker‑controlled arguments; the scan reports the file as safe, but pickle.load() triggers execution.
PoC
class PoC:
def __reduce__(self):
from numpy.f2py.crackfortran import _eval_length
return _eval_length, ("__import__('os').system('whoami')", None)
Impact
- Arbitrary code execution on the victim machine once they load the “scanned as safe” pickle / model file.
- Affects any workflow relying on Picklescan to vet untrusted pickle / PyTorch artifacts.
- Enables supply‑chain poisoning of shared model files.
Credits
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-71339 has been found in picklescan.
Attackers can target a specific entry point like numpy.f2py.crackfortran._eval_length over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade picklescan to 0.0.33 or later.
If unsure, ask your IT team or search "picklescan CVE-2025-71339" on the vendor's site.
CVE-2025-71339 (picklescan) — CWE-502 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: numpy.f2py.crackfortran._eval_length / __reduce__
Patched: 0.0.33 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in picklescan. Attackers reach the vulnerable code path via numpy.f2py.crackfortran._eval_length without authentication.
Check the vendor advisory for the affected versions of picklescan. Attack surface: numpy.f2py.crackfortran._eval_length / __reduce__.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.0.33.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'picklescan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'picklescan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
picklescanを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade picklescan to 0.0.33ステージング環境で 0.0.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web disclosure@vulncheck.com
- web github.com
- web pypi.org