← Back
CVE-2026-53874
critical
CVSS 9.8
Unsafe Deserialization in picklescan (CVE-2026-53874)
Summary
vulnerability in picklescan (CVE-2026-53874). Successful exploitation can lead to full system takeover. Exploitable via ``eval``. Mitigation: upgrade to `1.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53874** has been found in picklescan.
Attackers can target a specific entry point like ``eval`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade picklescan to **1.0.1** or later.
If unsure, ask your IT team or search "picklescan CVE-2026-53874" on the vendor's site.
CVE-2026-53874 (picklescan) — CWE-502 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `eval` / `getattr`
Patched: `1.0.1` — 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 ``eval`` without authentication.
📍 Affected scope
picklescan — . Attack surface: `eval` / `getattr`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.0.1**.
🛡️ 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 1.0.1ステージング環境で 1.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"1.0.1"}]}]
References
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://nvd.nist.gov/vuln/detail/CVE-2026-53874
- web [email protected]
- web https://github.com/advisories/GHSA-j6c9-qvp8-699f
- web https://github.com/mmaitre314/picklescan/pull/59
- web https://github.com/mmaitre314/picklescan/commit/173c8f2a869ea9b69b543477525ec70611c3c6f4
- web https://github.com/mmaitre314/picklescan/releases/tag/v1.0.1
- web https://github.com/advisories/GHSA-9m3x-qqw2-h32h