All reports
Medium

vllm: vLLM: Denial of Service via uninitialized log probability tensors

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-116180

Probability of exploitation in the next 30 days: 0.25%

FIRST EPSS · 2026-11-21

Description

vLLM from 0.8.5 before 0.31.0 has a denial of service flaw. LogprobsTensors.empty_cpu() in vllm/v1/outputs.py allocates an uninitialized int32 tensor, and the V1 model runner leaves prompt positions reported as computed by a KV connector unwritten. A client sharing the engine can send prompt_logprobs (or echo with logprobs) against a connector-cached prefix, making tokenizer decode raise OverflowError, which crashes EngineCore and drops all co-tenant requests.

A flaw was found in vLLM. A remote client sharing the inference engine can trigger a Denial of Service (DoS) by submitting requests with prompt log probabilities enabled against a cached prefix. Because uninitialized memory is allocated for log probability tensors, cached token positions remain unpopulated, causing the tokenizer to encounter invalid values during decoding. This causes an overflow error that crashes the core engine process and terminates all concurrent tenant requests.