← Back
CVE-2025-71339
high
CVSS 8.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in picklescan. Attackers reach the vulnerable code path via ``numpy.f2py.crackfortran._eval_length`` without authentication.
📍 Affected scope
picklescan — . Attack surface: `numpy.f2py.crackfortran._eval_length` / `__reduce__`.
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.33**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade picklescan to 0.0.33ステージング環境で 0.0.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
picklescan
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.33"}]}]
References
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/mmaitre314/picklescan/pull/53
- web https://github.com/mmaitre314/picklescan/commit/70c1c6c31beb6baaf52c8db1b6c3c0e84a6f9dab
- web https://github.com/mmaitre314/picklescan/releases/tag/v0.0.33
- web https://github.com/advisories/GHSA-6556-fwc2-fg2p
- web [email protected]