CVE
vLLM path traversal in speculators_config model loading
- 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 before 0.33.0 contains a path traversal vulnerability that allows malicious model publishers to redirect the served model and tokenizer by setting speculators_config verifier.name_or_path in config.json. Attackers can point this field at another local checkpoint directory to leak its tokenizer vocabulary via unauthenticated /detokenize requests and gain query access to private models.
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach12/20vllm: 578.2K downloads a week
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 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-130684 (vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_path), 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-130684 (entry last updated 2026-11-18):
Affected:
- PyPI package vllm: fixed in 0.33.0
Fixed versions: 0.33.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130684 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130684 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-qrj2-j723-m6w8
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-130684
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-130684"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- vllmPyPI
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
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · vllm-project/vllm · Advisory GHSA-qrj2-j723-m6w8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130684 |
| Record | NVD · CVE-2026-130684 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130684
Is CVE-2026-130684 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
Which versions are affected by CVE-2026-130684?
vllm (PyPI): before 0.33.0.Source: cve.now feed data
How do I fix CVE-2026-130684?
Upgrade to a fixed version: 0.33.0.Source: cve.now feed data