Live › vulnerability › CVE-2026-116181
Go to dashboardvLLM versions from 0.20.1 before 0.29.0 fail to validate stop_token_ids in requests, so an out-of-vocabulary ID can crash the inference engine. The same malformed input can also write outside the V2 runner's logits buffer.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-25 14:41 UTC. All times on this page are UTC.
Teams running vLLM between versions 0.20.1 and 0.29.0 that expose its OpenAI-compatible endpoints to clients they do not fully trust. Internal deployments with no untrusted callers are lower exposure. unknown whether the V2 runner is the default path in every configuration.
No product ranges from the sources yet.
pip show vllm or python -c "import vllm; print(vllm.__version__)"0.29.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
vLLM from 0.20.1 before 0.29.0 contains an improper input validation vulnerability that allows remote attackers to crash the engine by supplying out-of-vocabulary stop_token_ids. Attackers can send OpenAI chat, completion, generate, or batch requests with invalid IDs to terminate the engine or write outside the V2 runner's logits buffer.
This page as .md · .json · in your agent: get_signal("CVE-2026-116181")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.