Response amplification in OpenAI validation error handler
GHSA-mwgq-9582-w2vf · published 2026-11-07
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.30.0
An API client can trigger a disproportionately large error response. Formatting and sanitizing it consumes CPU and memory on the server, and buffering it can disrupt downstream clients and proxies. @rmonsurate originally reported the behavior on POST /v1/responses in issue #49239.
Upgrade vllm to 0.30.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.
The shared handler now limits the number of rendered errors and summarizes oversized input values before formatting. It still reports the total error count and how many entries were omitted. The fix bounds error-response rendering. Initial request validation and collection of validation errors still occur. A fix for this was introduced in https://github.com/vllm-project/vllm/pull/54684.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | >= 0.3.0, < 0.30.0 | 0.30.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.