High · CVSS 7.1CVE-2026-116181

vLLM 0.20.1 before 0.29.0 DoS and GPU Out-of-Bounds Write via stop_token_idsCVE-2026-116181

Answer in brief

CVE-2026-116181 records a High severity (CVSS 7.1) vulnerability in vLLM 0.20.1 before 0.29.0 DoS and GPU Out-of-Bounds Write via stop_token_ids. The current sources do not mark it as known exploited. The current feed maps vllm-project/vllm (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 25, 2026Updated Oct 25, 2026Source checked Oct 25, 2026First seen by HOL Oct 25, 2026Material review Oct 25, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps vllm-project/vllm (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
vllm-project/vllmgeneric	>=0.20.1 <0.29.0	0.29.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for vllm-project/vllm.
Review the reported fix. Update vllm-project/vllm to 0.29.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 25, 2026

Sources and claim methodology

Upstream source description

vLLM from 0.20.1 before 0.29.0 contains an improper input validation vulnerability that allows remote attackers to crash the engine by supplying out-of-vocabulary stop_token_ids. Attackers can send OpenAI chat, completion, generate, or batch requests with invalid IDs to terminate the engine or write outside the V2 runner's logits buffer.

Quoted source text, attributed separately from HOL analysis.