vLLM
vLLM before 0.29.0 Denial of Service via out-of-range stop_token_ids
vLLM before 0.29.0 accepts user-controlled stop_token_ids on the OpenAI-compatible POST /v1/completions and POST /v1/chat/completions endpoints but validates only that the values are integers, not that each token id is within the model vocabulary/logits range. When min_tokens > 0, the stop token ids are used as logits indices to suppress stop tokens, so an out-of-range id reaches a CUDA indexing operation (index_put_) and triggers a device-side assertion. An authenticated API user can send a single malformed completion request that returns 500 Internal Server Error and puts EngineCore into a fatal state, causing subsequent requests to fail until the service is restarted (denial of service).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.29.0
Fixed in 0.29.0
Mitigation
Upgrade vllm to 0.29.0 or later.
References
- Vendor advisory github.com/vllm-project/vllm/security/advisori…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.