UTC
Medium

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
What it is

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. …

What to do

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…

Affected
PackageRegistryAffectedFixed in
vllmPyPI>= 0.22.0, < 0.24.00.24.0

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].