vLLM denial of service via outlines unbounded cache on disk
CVE-2025-29770 · GHSA-mgrm-fgjv-mhv8 · published 2025-03-19 · updated 2026-06-08
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- 0.47%
- Fixed in
- 0.8.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
The outlines library is one of the backends used by vLLM to support structured output (a.k.a. guided decoding). Outlines provides an optional cache for its compiled grammars on the local filesystem. This cache has been on by default in vLLM. Outlines is also available by default through the OpenAI compatible API server. The affected code in vLLM is vllm/modelexecutor/guideddecoding/outlineslogitsprocessors.py, which unconditionally uses the cache from outlines. vLLM should have this off by default and allow administrators to opt-in due to the potential for abuse.
Upgrade vllm to 0.8.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.
https://github.com/vllm-project/vllm/pull/14837 The fix is to disable this cache by default since it does not provide an option to limit its size. If you want to use this cache anyway, you may set the VLLMV0USEOUTLINESCACHE environment variable to 1.
There is no way to workaround this issue in existing versions of vLLM other than preventing untrusted access to the OpenAI compatible API server.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | < 0.8.0 | 0.8.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.