← Back
CVE-2025-10155
Vulnerability in picklescan (CVE-2025-10155)
Summary
vulnerability in picklescan (CVE-2025-10155). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `0.0.31` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-10155** has been found in picklescan.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade picklescan to **0.0.31** or later.
If unsure, ask your IT team or search "picklescan CVE-2025-10155" on the vendor's site.
CVE-2025-10155 (picklescan) — CWE-20 /
Attack vector: local / unauthenticated
Patched: `0.0.31` — 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
**A vulnerability** (CWE-20) exists in picklescan.
📍 Affected scope
picklescan — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.0.31**.
🛡️ 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.31ステージング環境で 0.0.31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
picklescan
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.31"}]}]
pip
picklescan
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.31"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-10155
- package https://github.com/mmaitre314/picklescan
- web https://github.com/mmaitre314/picklescan/blob/58983e1c20973ac42f2df7ff15d7c8cd32f9b688/src/picklescan/scanner.py#L463
- web https://github.com/mmaitre314/picklescan/security/advisories/GHSA-jgw4-cr84-mqxg
- web https://github.com/mmaitre314/picklescan/commit/28a7b4ef753466572bda3313737116eeb9b4e5c5
- web https://github.com/pypa/advisory-database/tree/main/vulns/picklescan/PYSEC-2025-151.yaml
- web https://github.com/advisories/GHSA-jgw4-cr84-mqxg