vLLM Unauthenticated Requests Exploit DeepStream Backend Confusion for DoS
CVE-2026-78684 · GHSA-cqm8-jxg6-fqfq · published 2026-08-11 · updated 2026-09-01
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- Not scored
- Fixed in
- 0.27.0
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Partial
- CISA SSVC
This is a CWE-400 resource-consumption and partial denial-of-service vulnerability caused by GPU backend identity confusion and inconsistent enforcement of resource controls. An unauthenticated remote client can: activate DeepStream/NVDEC without startup configuration or GPU-memory reservation; choose the initial size of the process-wide DecodePool; bypass VLLM_MAX_IMAGE_PIXELS for DeepStream video requests; and degrade availability for unrelated requests through concurrent GPU video workloads. The demonstrated impact is partial and recoverable availability loss. …
Upgrade vllm to 0.27.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.
Register deepstream as a GPU-backed codec and apply the same GPU classification to loader and codec selection. Reject request-level DeepStream selection unless it was statically configured and included in startup GPU-memory reservation. Fail closed for unknown request-level backend names. Call _check_frame_pixel_limit(width, height) immediately after probe_metadata(). Make pool_size startup-only rather than request-controlled. Add a total decoded-work limit based on selected frames × width × height. Add regression tests for request-level DeepStream selection and OpenCV/DeepStream pixel-limit parity.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | < 0.27.0 | 0.27.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 (published by vLLM). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.