# CVE-2026-92220: vllm-project vLLM MoRIIO Acknowledgement moriio_connector.py MoRIIOWrapper._handle_release_message resource consumption

> Remote attackers can cause resource consumption in vLLM by manipulating request parameters in the MoRIIO connector, leading to denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-72xc-v4m3-9r7g

## What is CVE-2026-92220?

CVE-2026-92220 is a medium-severity denial of service vulnerability in vllm-project vLLM, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in vllm-project vLLM 0.26.0/0.27.0. Affected is the function MoRIIOConnectorScheduler.request_finished/MoRIIOConnectorWorker.get_finished/MoRIIOWrapper._handle_release_message of the file vllm/distributed/kv_transfer/kv_connector/v1/moriio/moriio_connector.py of the component MoRIIO Acknowledgement Handler. Performing a manipulation of the argument request_id/kv_transfer_params results in resource consumption. It is possible to initiate the attack remotely. The project was informed of the problem early through a pull request but has not reacted yet.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

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


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

No fix has been published for CVE-2026-92220 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92220 is a medium-severity denial of service vulnerability in vllm-project vLLM, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92220 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-92220/ (Markdown: https://insights.sbomify.com/CVE-2026-92220/index.md)
```

## Sources

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

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