← Back
CVE-2025-32444
Unsafe Deserialization in vllm (CVE-2025-32444)
Summary
vulnerability in vllm (CVE-2025-32444). Successful exploitation can lead to full system takeover. Exploitable via ``pickle``. Mitigation: upgrade to `0.8.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-32444** has been found in vllm.
Attackers can target a specific entry point like ``pickle`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade vllm to **0.8.5** or later.
If unsure, ask your IT team or search "vllm CVE-2025-32444" on the vendor's site.
CVE-2025-32444 (vllm) — CWE-502 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `pickle`
Patched: `0.8.5` — 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 vllm. Attackers reach the vulnerable code path via ``pickle`` without authentication.
📍 Affected scope
vllm — . Attack surface: `pickle`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.8.5**.
🛡️ 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 'vllm' .` 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 'vllm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vllm` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade vllm to 0.8.5ステージング環境で 0.8.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0.6.5"},{"fixed":"0.8.5"}]}]
References
- advisory https://github.com/advisories/GHSA-hj4w-hm2g-p6w5
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-32444
- package https://github.com/vllm-project/vllm
- web https://github.com/vllm-project/vllm/security/advisories/GHSA-hj4w-hm2g-p6w5
- web https://github.com/vllm-project/vllm/security/advisories/GHSA-x3m8-f7g5-qhm7
- web https://github.com/vllm-project/vllm/commit/a5450f11c95847cf51a17207af9a3ca5ab569b2c
- web https://github.com/vllm-project/vllm/blob/32b14baf8a1f7195ca09484de3008063569b43c5/vllm/distributed/kv_transfer/kv_pipe/mooncake_pipe.py#L179
- web https://github.com/pypa/advisory-database/tree/main/vulns/vllm/PYSEC-2025-42.yaml