Rust gRPC CandidateTokens.top_n bypasses max_logprobs and can terminate EngineCore
GHSA-rwfw-xvg3-3937 · published 2026-10-09 · updated 2026-10-27
- Severity
- Medium
- CVSS score
- 5.9
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 0.24.0
An attacker who can reach a vLLM Rust gRPC endpoint can send a small gRPC request with output_logprobs = true and an oversized output_candidates.top_n, or with prompt_logprobs = true and an oversized prompt_candidates.top_n. Expected impact is single-request denial of service for affected deployments: the Rust gRPC frontend accepts the count, forwards it to engine-core sampling state, and the lower V1 logprob path can raise after execution begins. EngineCore treats uncaught worker exceptions as fatal engine errors. This report does not claim code execution, data access, model compromise, persistence, or public internet exposure. …
Upgrade vllm to 0.24.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 CandidateTokens.top_n in rust/src/server/src/grpc/convert.rs before assigning params.logprobs or params.prompt_logprobs. Recommended patch shape: replace *n as i32 with a checked conversion; reject values larger than i32::MAX; reject values larger than the configured model/server max_logprobs, unless the operator explicitly configured no-cap max_logprobs = -1; preserve the explicit all selector as the only way to request full-vocab logprobs; return Status::invalid_argument(...) before submitting any engine request; and add unary Generate and streaming GenerateStream regression tests for: top_n = 20 accepted under default config; top_n = 21 rejected under default config; top_n = 1_0…
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| vllm | PyPI | >= 0.22.0, < 0.24.0 | 0.24.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.