# CVE-2026-92365: vllm-project vllm thinking_budget_state.py algorithmic complexity

> Remote attackers can cause denial of service in vLLM by exploiting inefficient algorithmic complexity in the thinking budget state module.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-mcqv-hjvx-mmqr

## What is CVE-2026-92365?

CVE-2026-92365 is a medium-severity denial of service vulnerability in vllm-project vllm, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in vllm-project vllm up to 0.29.0. Affected by this issue is some unknown functionality of the file vllm/v1/sample/thinking_budget_state.py. The manipulation results in inefficient algorithmic complexity. It is possible to launch the attack remotely. The pull request to fix this issue awaits acceptance.

Weakness: CWE-407 (Inefficient Algorithmic Complexity), CWE-404 (Improper Resource Shutdown or Release)

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


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

Apply the vendor's patch.

## Is CVE-2026-92365 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92365 is a medium-severity denial of service vulnerability in vllm-project vllm, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92365 in the wild and no public exploit code.

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

## Sources

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

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