Vulnerability in vllm (CVE-2026-55514)
Summary
Vulnerability in vllm (CVE-2026-55514). Risk of unauthorized operations or information disclosure. Exploitable via _init_mrope_positions. Mitigation: upgrade to 0.24.0 or later.
Original description
The description as published by the source.
vLLM is a library for LLM inference and serving. From 0.12.0 to before 0.24.0, sending a pure prompt embeds payload in a /v1/completions request with a model using M-RoPE causes EngineCore to fail an assertion and fatally crash, shutting down the entire server application. Any remote user who is authorized to make a /v1/completions request can make such a request and induce a crash. This issue is fixed in version 0.24.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55514 has been found in vllm.
Attackers can target a specific entry point like _init_mrope_positions over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade vllm to 0.24.0 or later.
If unsure, ask your IT team or search "vllm CVE-2026-55514" on the vendor's site.
CVE-2026-55514 (vllm) — CWE-617 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: _init_mrope_positions / GPUModelRunner / None / mrope_model.get_mrope_input_positions
Patched: 0.24.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.
A vulnerability (CWE-617) exists in vllm. Attackers reach the vulnerable code path via _init_mrope_positions.
Check the vendor advisory for the affected versions of vllm. Attack surface: _init_mrope_positions / GPUModelRunner / None / mrope_model.get_mrope_input_positions.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.24.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vllm to 0.24.0ステージング環境で 0.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com