Skip to main content
Menu
CVEs

CVE

vLLM unauthenticated DoS in EngineCore via token IDs

Affects vLLM 0.28.0 before 0.33.0 when run with --skip-tokenizer-init, the mode where no tokenizer is loaded. Fixed in 0.33.0.

CVE-2026-130685Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.33.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.33.0.

Summary

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.

Who should check

Teams running vLLM 0.28.0 up to 0.33.0 with --skip-tokenizer-init, such as token-in-token-out or RL serving setups.

Not fixed by: Earlier GHSA-25q3-v2hm-8vpf remediation did not cover the tokenizer-disabled path.

“--skip-tokenizer-init is the mode where the client is expected to send raw”

github.com

cve.now Index

41Pcve.now Index 41 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach12/20vllm: 578.2K downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active
  • Would score about 46 if advisories confirm default setups are exposed

Impact

  • Widely used

    vllm has 578.2k weekly downloads.Source: pypistats.org

    93 packages depend on vllm.Source: deps.dev

What to do

  • Upgrade to a fixed version: 0.33.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130685 (vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token ID), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130685 (entry last updated 2026-11-18):
Affected:
- PyPI package vllm: from 0.28.0, fixed in 0.33.0
Fixed versions: 0.33.0.
Conditions (all must be true for the bug to be hit):
- Affects vLLM versions from 0.28.0 before 0.33.0. (source: https://github.com/vllm-project/vllm/security/advisories/GHSA-q9v9-qpjp-fc24)
- Server must run with --skip-tokenizer-init, so no tokenizer is loaded. (source: https://github.com/vllm-project/vllm/security/advisories/GHSA-q9v9-qpjp-fc24)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130685 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130685 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vllm-project/vllm/security/advisories/GHSA-q9v9-qpjp-fc24
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130685
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130685"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • vllmPyPI

    From 0.28.0 · fixed in 0.33.0

    Fixed in 0.33.0 (released Nov 2, 2026, 16 days before disclosure).

    The latest release, 0.33.0, is not affected.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · vllm-project/vllm · Advisory GHSA-q9v9-qpjp-fc24
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130685
RecordNVD · CVE-2026-130685

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130685

Is CVE-2026-130685 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A single unauthenticated request with a large out-of-range token ID crashes the shared engine, denying service to all users until the server is restarted.Source: github.com

Which versions are affected by CVE-2026-130685?

vllm (PyPI): from 0.28.0 before 0.33.0.Source: cve.now feed data

Am I affected, and how do I check?

vLLM versions from 0.28.0 before 0.33.0 that run with --skip-tokenizer-init, where no tokenizer is loaded and the client sends raw token IDs. To check, look at the installed version with pip show vllm and at whether the server was started with --skip-tokenizer-init.Source: github.com

How do I fix CVE-2026-130685?

Upgrade vLLM to 0.33.0 or later, which is the version range's fixed release.Source: github.com

More CVEs