vLLM: Derender endpoints decode caller-supplied GenerateResponse token IDs without output bounds
CVE-2026-71486 · GHSA-8737-qx52-hjff · published 2026-09-04
- Severity
- Medium
- CVSS score
- 4.3
- Chance of exploitation (EPSS)
- 0.37%
- Fixed in
- 0.26.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An attacker with access to the /v1 API can send derender requests that consume CPU and memory in the frontend/postprocessing process and can cause large responses unrelated to any bounded generation. In disaggregated deployments, this affects the CPU-only render frontend; in servers where the render router is attached alongside generation, it affects the same OpenAI-compatible server process that handles normal client traffic. This can degrade availability for other clients sharing the process. Likely CWE: CWE-400 (Uncontrolled Resource Consumption) / CWE-770 (Allocation of Resources Without Limits or Throttling). Conservative CVSS v3.1: (4.3).
Upgrade vllm to 0.26.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.
Validate derender payloads before any detokenization or parser invocation. Apply bounded limits to generateresponse(s), choices, tokenids, promptlogprobs, logprobs.content, toplogprobs, and routedexperts that are at least as strict as the corresponding generation-side limits. For completions, reject generateresponses counts above the number of prompts that /v1/completions/render would have produced, and reject total nested choice counts above maxnumseqs / n limits.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | < 0.26.0 | 0.26.0 |
- HightsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS@tsparticles/mcp-server
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighHTTP server transports and OAuth endpoints read request bodies with no size limitmcp, mcp
- HighLMDeploy vulnerable to arbitrary code execution via eval() of untrusted quant_dtype in model config loadinglmdeploy
- HighRMCP: Unauthenticated permanent session-table leak in rmcp Streamable HTTP server transport leads to remote denial-of-servicermcp
- 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 (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.