Technical impact
A flaw in vLLM causes the LogprobsTensors.empty_cpu() function to allocate an uninitialized int32 tensor, and the V1 model runner leaves certain prompt positions unwritten. If a client sends a prompt_logprobs or echo request that relies on a connector‑cached prefix, the tokenizer decoding path can trigger an OverflowError. The error propagates to EngineCore, causing the whole engine process to crash and dropping all in‑flight requests from every tenant sharing the instance. The result is a denial of service that disables service for all tenants attached to the affected engine.
Affected Systems
vLLM, version 0.8.5 through 0.30.x (inclusive), any installation that uses the multi‑tenant server mode. The vulnerability is limited to those releases before the 0.31.0 fix.
Risk and Exploitability
The CVSS score of 8.3 indicates a high severity issue. EPSS is unavailable, and the vulnerability is not listed in CISA KEV. The likely attack vector requires an attacker who can submit inference requests to a shared vLLM engine; by crafting a prompt_logprobs or echo request against a cached prefix the attacker can trigger the OverflowError and crash the engine. The exploit therefore targets multi‑tenant deployments, with the risk being that a single malicious tenant can indiscriminately disrupt all co‑tenant workloads.