CVE-2026-55514: vllm · Reachable Assertion
Affects vllmSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 0.24.0 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.24.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade vllm and vllm-project/vllm to 0.24.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vllm-projectvllm | Affected
| Fixed in
|
GitHubvllm-project/vllmpkg:github/vllm-project/vllmOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade vLLM to version 0.24.0 or later where this assertion failure vulnerability is fixed. No other mitigation or workaround is documented. Patch status is confirmed by the vendor advisory stating the fix is in 0.24.0.
Description
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.
References
- github.com/vllm-project/vllm/security/advisories/GHSA-33cg-gxv8-3p8g (opens in a new tab)
- github.com/vllm-project/vllm/pull/45252 (opens in a new tab)
- github.com/vllm-project/vllm/commit/470229c37efaf69c86e8bc97482b0b1ff7551c65 (opens in a new tab)
- github.com/vllm-project/vllm/releases/tag/v0.24.0 (opens in a new tab)