# CVE-2026-90713: vllm-project vLLM tiktoken vocab File mod.rs new denial of service

> Local attackers can cause a denial of service in vLLM via the tiktoken vocab file handler, requiring a patch for mitigation.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-hvv2-qg7m-ffqp

## What is CVE-2026-90713?

CVE-2026-90713 is a medium-severity denial of service vulnerability in vllm-project vLLM, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in vllm-project vLLM up to 0.29.0. The affected element is the function TiktokenTokenizer::new of the file rust/src/text/src/backend/hf/mod.rs of the component tiktoken vocab File Handler. The manipulation results in denial of service. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The pull request to fix this issue awaits acceptance.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

Apply the vendor's patch.

## Is CVE-2026-90713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90713 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90713 is a medium-severity denial of service vulnerability in vllm-project vLLM, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90713 exists.

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

## Sources

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

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