GHSA-87x5-vmc3-756j vLLM: Completion prompt lists fan out into unbounded engine requests
SummaryThe `/v1/completions` request model accepts `prompt` as a list of text prompts or a list of token-id prompts without any outer prompt-count bound. The serving path turns each element into a separate engine input, creates one engine generator per element, merges all generators, and allocates a response slot per prompt. An authenticated API client can therefore turn one request into an attacker-chosen number of backend subrequests before any aggregate request-count budget is enforced.Technical Details`CompletionRequest.prompt` allows both list-shaped prompt inputs and scalar prompts:The validator only requires some prompt-like input to be present:The renderer then expands list-shaped prompts as a sequence. `prompt_to_seq()` wraps a scalar string or a single token-id list, but returns a `list[str]` or `list[list[int]]` unchanged:`OnlineRenderer.preprocess_completion()` appends that whole sequence, and the renderer processes every element:Finally, completion serving creates one backend generator and one response slot per rendered prompt:The violated invariant is that one HTTP request should have a bounded backend request count. Current code enforces per-prompt token and sampling limits, but not the number of prompts in the outer completion request.PoVA minimal oversized request keeps normal generation parameters small but supplies a large outer prompt list:Scaling the `prompt` array to tens or hundreds of thousands of short entries makes the server allocate, preprocess, schedule, merge, and buffer one subrequest per entry. The same applies to token-id prompt lists:The intended negative control is a scalar prompt:The scalar string is wrapped as one prompt; the list form is not bounded and fans out by list length.ImpactAn authenticated API client can make one `/v1/completions` request consume CPU, memory, async task scheduling, engine request slots, and response buffering proportional to an attacker-chosen outer prompt list. This can starve or disrupt other tenants sharing the same vLLM server. The report does not claim unauthenticated access, confidentiality impact, integrity impact, code execution, or impact where `/v1/completions` is not reachable by untrusted or semi-trusted clients.Suggested FixReject oversized prompt lists before renderer preprocessing. Add an outer prompt-count limit to `CompletionRequest.prompt` when the prompt is `list[str]` or `list[list[int]]`, and consider making the limit configurable in the same style as the batch-chat and sampling-list bounds. The check should run before `OnlineRenderer.preprocess_completion()` expands the prompt sequence, so oversized requests do not allocate parsed prompt lists, async render/tokenization tasks, engine generators, or response result slots.Regression coverage should include a scalar prompt, a bounded prompt list, an oversized `list[str]`, and an oversized `list[list[int]]`. The oversized requests should fail with a controlled validation error before any backend generator is created.Affected Package/VersionsPackage ecosystem: pipPackage name: `vllm`Affected range confirmed by source proof: `>=0.19.0, <=0.24.0`; current `main` at `cbe9c40f998f13975b967773ac7e7920e115387f` remains affected.Patched versions: unknown.Latest release checked: `v0.24.0`, published on 2026-06-29.GitHub Advisory MetadataPackage ecosystem: pipPackage name: `vllm`Vulnerable version range: `>=0.19.0, <=0.24.0`Patched versions: unknownAdvisory HistoryPublic issue and PR searches for `CompletionRequest prompt list`, `"prompt" "list[str]" "completion"`, and `"CompletionRequest" "max_length"` did not find an existing report or fix for this exact path.The closest published advisory is `GHSA-3mwp-wvh9-7528`, "OOM Denial of Service via Unbounded `n` Parameter in OpenAI API Server", patched in `0.19.0`. This report is distinct because it keeps `n=1` and uses the `/v1/completions` `prompt` outer list to create one engine request per prompt. The fix invariant is an outer prompt-count and aggregate request budget, not only a generated-sequence-count cap.The closest public PR is `vllm-project/vllm#45390`, which covers multiple DoS fixes including `GHSA-83mh-6mwq-3hg9` for `BatchChatCompletionRequest.messages`. That PR adds an outer bound to batch chat conversations, but its diff does not touch `vllm/entrypoints/openai/completion/protocol.py` or `vllm/entrypoints/openai/completion/serving.py`.Prior local/private report families checked included pooling/rerank batch fanout, derender token-id postprocessing, explicit `truncation_side` tokenizer-limit bypass, Python disaggregated generate prompt-length bypass, and priority scheduling. Those reports differ by endpoint, attacker-controlled field, sink, and fix surface.
CVSS v3.1 score: 6.5