← Back
CVE-2026-41523
high
CVSS 7.5
Code Injection in vllm (CVE-2026-41523)
Summary
code injection in vllm (CVE-2026-41523). Successful exploitation can lead to full system takeover. Exploitable via ``assert``. Mitigation: upgrade to `0.22.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41523** has been found in vllm.
Attackers can target a specific entry point like ``assert`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade vllm to **0.22.0** or later.
If unsure, ask your IT team or search "vllm CVE-2026-41523" on the vendor's site.
CVE-2026-41523 (vllm) — CWE-94 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `assert` / `function_name` / `resolve_obj_by_qualname`
Patched: `0.22.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
**arbitrary code execution** (CWE-94) exists in vllm. Attackers reach the vulnerable code path via ``assert`` without authentication.
📍 Affected scope
vllm — . Attack surface: `assert` / `function_name` / `resolve_obj_by_qualname`.
🔥 Severity
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.22.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 '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.22.0ステージング環境で 0.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0"}]}]
References
- advisory [email protected]
- exploit [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-q8gq-377p-jq3r
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c