Description
vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, a frontend-legal multi-request speculative decoding workload can cause the rejection sampler to produce a recovered token equal to the model vocabulary size boundary value, which is then converted to negative one when the engine selects the next live token for a request and is written back into the drafter's input ids; that out-of-vocabulary value is later consumed by the model's embedding and attention path and crashes the engine worker with a GPU device-side assertion. The same triggering request sequence is reachable through the public gRPC Generate and Abort endpoints, so a remote client that can send generation requests can crash the shared engine worker, aborting concurrent requests and causing a service-wide denial of service for other clients of the deployment until the worker is restarted. This issue is fixed in version 0.24.0.
Published: 2026-07-06
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

vLLM is a high-throughput inference engine for large language models. In releases prior to 0.24.0, speculative decoding can generate a recovered token equal to the vocabulary size boundary; this value is converted to –1 and passed to the model’s embedding and attention paths, triggering an out-of-bounds assertion and crashing the worker. The crash aborts all concurrent requests, resulting in a service-wide denial of service for any client sharing the worker.

Affected Systems

vllm-project vLLM versions earlier than 0.24.0, especially deployments that share a single engine worker across multiple clients; the flaw can be triggered through the public gRPC Generate and Abort endpoints.

Risk and Exploitability

With a CVSS score of 7.5, the vulnerability is classified as high severity, but an EPSS score of <1% indicates a very low current exploitation probability and it is not listed in the CISA KEV catalog. An attacker only needs the ability to send generation requests to the exposed gRPC endpoints; no local or privileged access is required. By crafting a specific request sequence that induces speculative decoding, the attacker can cause the shared worker to crash and deny service to all users until a restart occurs.

Generated by OpenCVE AI on July 23, 2026 at 14:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to vLLM 0.24.0 or later, which introduces bounds checking for recovered token indices and corrects the out‑of‑bounds handling (CWE‑125).
  • Add or enforce input validation that ensures any token passed to the engine lies within the vocabulary range [0, vocab_size-1] and is non‑negative (CWE‑20).
  • Implement a runtime guard that detects a recovered token equal to the vocabulary size boundary or a negative value and replaces it with a safe default token before further processing (CWE‑1284).
  • Restrict access to the public gRPC Generate and Abort endpoints to authorized clients only, reducing the exposure to the speculative decoding trigger (CWE‑20).
  • Deploy a health‑check or automatic restart mechanism to recover the worker promptly if it crashes, minimizing service disruption.

Generated by OpenCVE AI on July 23, 2026 at 14:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8wr5-jm2h-8r4f vLLM has Remote DoS via Invalid Recovered Token Reinjection
History

Wed, 08 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-125
References
Metrics threat_severity

None

threat_severity

Important


Tue, 07 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 06 Jul 2026 22:15:00 +0000

Type Values Removed Values Added
First Time appeared Vllm-project
Vllm-project vllm
Vendors & Products Vllm-project
Vllm-project vllm

Mon, 06 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Description vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Prior to 0.24.0, a frontend-legal multi-request speculative decoding workload can cause the rejection sampler to produce a recovered token equal to the model vocabulary size boundary value, which is then converted to negative one when the engine selects the next live token for a request and is written back into the drafter's input ids; that out-of-vocabulary value is later consumed by the model's embedding and attention path and crashes the engine worker with a GPU device-side assertion. The same triggering request sequence is reachable through the public gRPC Generate and Abort endpoints, so a remote client that can send generation requests can crash the shared engine worker, aborting concurrent requests and causing a service-wide denial of service for other clients of the deployment until the worker is restarted. This issue is fixed in version 0.24.0.
Title vLLM: Remote DoS in vLLM via Invalid Recovered Token Reinjection
Weaknesses CWE-1284
CWE-20
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

Vllm-project Vllm
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-07T14:13:34.348Z

Reserved: 2026-06-12T16:25:43.084Z

Link: CVE-2026-54234

cve-icon Vulnrichment

Updated: 2026-07-07T14:13:30.358Z

cve-icon NVD

No data.

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-06T19:49:20Z

Links: CVE-2026-54234 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-23T14:30:17Z

Weaknesses
  • CWE-125

    Out-of-bounds Read

  • CWE-1284

    Improper Validation of Specified Quantity in Input

  • CWE-20

    Improper Input Validation