# CVE-2026-130685: vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token ID


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-cf32-wrp7-cjrw, GHSA-q9v9-qpjp-fc24

## What is CVE-2026-130685?

CVE-2026-130685 is a high-severity vulnerability in vllm-project vllm, published on 18 Nov 2026. 

### Official description

vLLM from 0.28.0 before 0.33.0 contains an improper input validation vulnerability that allows unauthenticated attackers to crash the shared EngineCore by sending out-of-range prompt token ids when served with --skip-tokenizer-init. Attackers can submit a large positive token id to /v1/completions, /v1/embeddings, or /pooling, bypassing the tokenizer-gated vocab check and causing a fatal embedding index error that denies service to all tenants.

Weakness: CWE-20 (Improper Input Validation)

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

1 open source package ship an affected version, including vllm.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `vllm` | PyPI | `pkg:pypi/vllm` | From 0.28.0 | 0.33.0 |

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

Upgrade vllm to 0.33.0 or later.

## Is CVE-2026-130685 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- vllm (PyPI): affected from 0.28.0; fixed in 0.33.0

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-130685/ (Markdown: https://insights.sbomify.com/CVE-2026-130685/index.md)
```

## Sources

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

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