# CVE-2026-114051: vLLM before 0.31.0 Denial of Service via min_tokens in /inference/v1/generate


- **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:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-4xqp-c3mv-qff7, GHSA-qwv5-gq8g-3jwj

## What is CVE-2026-114051?

CVE-2026-114051 is a high-severity vulnerability in vllm-project vllm, published on 21 Oct 2026. 

### Official description

vLLM before 0.31.0 skips the min_tokens <= max_tokens check for /inference/v1/generate requests with a null max_tokens, so the EngineCore input thread later dies on an uncaught VLLMValidationError while /health still returns 200. Unauthenticated remote attackers can send one request with an oversized min_tokens to hang all subsequent generation requests until manual restart.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-114051 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: vllm-project 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-114051/ (Markdown: https://insights.sbomify.com/CVE-2026-114051/index.md)
```

## Sources

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

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