Thinking-budget sparse state aliases onto a co-batched request during a mixed `SWAP`, forcing the reasoning-end token into another request's
GHSA-fpch-3xrf-7q96 · published 2026-11-09
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.28.0
thinking_token_budget is a public sampling parameter on the OpenAI-compatible completion route. When the budget is reached, vLLM forces the configured reasoning-end token sequence (e.g. ) into the request's output. On the legacy V1 model runner this state is tracked in ThinkingBudgetStateHolder, a sparse dictionary keyed by mutable batch-row index. ThinkingBudgetStateHolder.sync_batch() implements its own row-move logic. Its SWAP branch reads both endpoints with get() and reassigns them, but never removes the source entries. …
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | >= 0.21.0, < 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.