# CVE-2026-116181: vLLM 0.20.1 before 0.29.0 DoS and GPU Out-of-Bounds Write via stop_token_ids


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-f2x4-7hx3-gxfp, GHSA-w9r6-29q4-pvpr

## What is CVE-2026-116181?

CVE-2026-116181 is a high-severity vulnerability in Vllm Vllm, published on 25 Oct 2026. 

### Official 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.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2026-116181?

It affects 1 product.


Products: Vllm Vllm.

## How do I fix CVE-2026-116181?

No fix has been published for CVE-2026-116181 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116181 being exploited?

There is no known exploitation of CVE-2026-116181 in the wild and no public exploit code.

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2024-11041](https://insights.sbomify.com/CVE-2024-11041/): Remote Code Execution in vllm-project/vllm (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116181 and fix it if it is affected.

What it is: CVE-2026-116181 is a high-severity vulnerability in Vllm Vllm, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116181 in the wild and no public exploit code.

Affected product: Vllm Vllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116181/ (Markdown: https://insights.sbomify.com/CVE-2026-116181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116181
- OSV: https://osv.dev/vulnerability/CVE-2026-116181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116181/
Summaries are generated and may contain mistakes; the official description above is the record.