CVE-2026-130685: vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token ID
vLLM from 0.28.0 before 0.33.0 contains an improper input validation vulnerability that allows unauthenticated attackers to crash the shared EngineCore by sending out-of-range prompt token ids when served with --skip-tokenizer-init. Attackers can submit a large positive token id to /v1/completions, /v1/embeddings, or /pooling, bypassing the tokenizer-gated vocab check and causing a fatal embedding index error that denies service to all tenants.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this denial-of-service issue?
vLLM deployments running versions from 0.28.0 before 0.33.0 are exposed when they are served with --skip-tokenizer-init. The impact is greatest for shared EngineCore deployments, because crashing the EngineCore denies service to all tenants.
What does an attacker need to do to trigger the crash?
No authentication or user interaction is required. An attacker can send a large positive, out-of-range prompt token ID to the /v1/completions, /v1/embeddings, or /pooling endpoint, causing a fatal embedding index error.
Are ordinary tokenizer-enabled deployments affected?
The described attack relies on --skip-tokenizer-init, which bypasses the tokenizer-gated vocabulary check. The provided information does not identify tokenizer-enabled deployments as affected by this specific exploit path.
How can operators determine whether they may be vulnerable?
Check whether the vLLM version is 0.28.0 or later but earlier than 0.33.0, and whether the service is started with --skip-tokenizer-init. Also review whether the listed endpoints accept prompt token IDs from unauthenticated callers.