← Back
CVE-2026-54236
medium
CVSS 5.3
Vulnerability in vllm (CVE-2026-54236)
Summary
vulnerability in vllm (CVE-2026-54236). Risk of unauthorized operations or information disclosure. Exploitable via `POST /v1/messages`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54236** has been found in vllm.
Attackers can target a specific entry point like `POST /v1/messages` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "vllm CVE-2026-54236" on the vendor's site.
CVE-2026-54236 (vllm) — CWE-532 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /v1/messages / POST /v1/messages/count_tokens / `sanitize_message` / `UnidentifiedImageError`
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-532) exists in vllm. Attackers reach the vulnerable code path via `POST /v1/messages` without authentication.
📍 Affected scope
vllm — . Attack surface: POST /v1/messages / POST /v1/messages/count_tokens / `sanitize_message` / `UnidentifiedImageError`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `POST /v1/messages` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /v1/messages' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /v1/messages` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /v1/messages on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
vllm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]