Description
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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| vllm-project | vllm | < 0.29.0 | 0.29.0 |
Advisories 1
- WID-SEC-2026-3327 vllm: Mehrere Schwachstellen ermöglichen BSI CERT-Bund (WID) · Nov 9, 2026
References
- GitHub Security Advisory (GHSA-v5gm-qgmv-gc6c) vendor-advisory
- VulnCheck Advisory: vLLM before 0.29.0 Denial of Service via out-of-range stop_token_ids third-party-advisory