UTC
Medium

Rust gRPC Generate accepts out-of-vocabulary prompt token IDs and can terminate EngineCore

GHSA-w2v2-5662-8v5q · 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 submit a Generate or GenerateStream request with an out-of-vocabulary prompt.token_ids value. The request is accepted by the gRPC frontend and submitted to the shared text generation path. The same invalid token-id sink is documented publicly in PR #45441 as aborting EngineCore for the Rust HTTP sibling route. Expected impact is a single-request denial of service for deployments exposing the Rust gRPC service. Fixed behavior should be an INVALID_ARGUMENT gRPC status before the request is submitted to the engine. …

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.

Apply the same token-id range validation used by the Rust OpenAI and HTTP generate routes before either gRPC handler calls state.chat.text().generate(). The gRPC fix should validate: GenerateRequest.prompt.token_ids against the same prompt bound used by PR #45441, namely the union of tokenizer and model vocabulary bounds. DecodingParameters.allowed_token_ids against tokenizer vocabulary. DecodingParameters.logit_bias keys against model vocabulary. and , if they are lowered into logprob_token_ids, against the same model/tokenizer bounds used by the corresponding HTTP route. …

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