Denial of service: a negative token id in `/v1/embeddings` or `/pooling` input kills the vLLM engine via a CUDA device-side assertion
CVE-2026-93592 · GHSA-25q3-v2hm-8vpf · published 2026-09-03 · updated 2026-09-30
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- Not scored
- Fixed in
- 0.28.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
Any deployment that serves a pooling or embedding model through the OpenAI-compatible API server. One unauthenticated HTTP request is a complete denial of service for that server process and every client using it. Restarting under a supervisor does not mitigate it, because the same request can be sent again immediately. Confidentiality and integrity are unaffected; the impact is availability only.
Upgrade vllm to 0.28.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Fixed in 0.28.0 by https://github.com/vllm-project/vllm/pull/51795 (commit b216db3ed0), which adds the missing lower-bound check to InputProcessor._validate_model_input so a negative id is rejected as HTTP 400 before the ids reach the device: The validation path is shared by generate, embedding and pooling requests, so the check covers all three.
For deployments that cannot upgrade to 0.28.0: Reject request bodies containing negative integers in input at a reverse proxy or API gateway in front of vLLM. Do not expose the token-id form of the input; accept only string input from untrusted callers. Restrict network access to /v1/embeddings and /pooling. Process supervision is not a workaround: the request can simply be repeated.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | < 0.28.0 | 0.28.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalvLLM: OpenAI auth bypassvllm
- CriticalvLLM has RCE In Video Processingvllm
- CriticalvLLM Allows Remote Code Execution via PyNcclPipe Communication Servicevllm
- CriticalvLLM Vulnerable to Remote Code Execution via Mooncake Integrationvllm
- CriticalCVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0vllm
- CriticalvLLM Deserialization of Untrusted Data vulnerabilityvllm
The impact, patch and workaround text comes from the advisory, shortened (published by vLLM). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.