# CVE-2026-130684: vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_path


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/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-9f95-xfwr-j77p, GHSA-qrj2-j723-m6w8

## What is CVE-2026-130684?

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

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

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

Upgrade vllm to 0.33.0 or later.

## Is CVE-2026-130684 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- vllm (PyPI): affected all versions; 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-130684/ (Markdown: https://insights.sbomify.com/CVE-2026-130684/index.md)
```

## Sources

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

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