Vulnerability in pypickle (CVE-2025-5174)

Summary

vulnerability in pypickle (CVE-2025-5174). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2025-5174** has been found in pypickle. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: upgrade pypickle to **14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0** or later. If unsure, ask your IT team or search "pypickle CVE-2025-5174" on the vendor's site.

CVE-2025-5174 (pypickle) — Attack vector: local / no user interaction Patched: `14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0` — 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** (unclassified) exists in pypickle.

📍 Affected scope

pypickle — .

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover

🔧 How to fix

Update to **14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0**.

🛡️ 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 'pypickle' .` 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

1
Identify exposure identify
```
grep -r 'pypickle' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pypickle` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade pypickle to 14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0
```
ステージング環境で 14b4cae704a0bb4eb6723e238f25382d847a1917, 5058ea8c0666b3f8d30893be5c0132ad7fb7bf39, 2.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI pypickle

[{"repo":"https:\/\/github.com\/erdogant\/pypickle","type":"GIT","events":[{"introduced":"0"},{"fixed":"14b4cae704a0bb4eb6723e238f25382d847a1917"},{"fixed":"5058ea8c0666b3f8d30893be5c0132ad7fb7bf39"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}]