---
title: "CVE-2026-94626: vLLM - Denial of Service"
description: "vLLM through 0.29.0 contains an unbounded memory allocation vulnerability caused by failure to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, letting attackers exhaust memory and trigger kernel OOM-kill, exploit requires attacker to supply arbitrary tp_size values in prefill/decode disaggregated deployments."
url: https://panop.io/threat-heartbeat/CVE-2026-94626/
---

# CVE-2026-94626 vLLM - Denial of Service

vLLM through 0.29.0 contains an unbounded memory allocation vulnerability caused by failure to validate the tp\_size parameter in kv\_transfer\_params on OpenAI-compatible completion endpoints, letting attackers exhaust memory and trigger kernel OOM-kill, exploit requires attacker to supply arbitrary tp\_size values in prefill/decode disaggregated deployments.

CVSS base score 7.5 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.63% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-94626)

## Details

Type

Denial of Service

Impact

Denial Of Service

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Published

21 September 2026

Updated

15 October 2026

Weakness

[CWE-789](https://cwe.mitre.org/data/definitions/789.html)

## Vendor fix

Update to the latest version beyond 0.29.0.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-94626](https://nvd.nist.gov/vuln/detail/CVE-2026-94626)
- [https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv\_transfer/kv\_connector/v1/nixl/metadata.py#L277](https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277)
- [https://github.com/vllm-project/vllm/pull/51137](https://github.com/vllm-project/vllm/pull/51137)
- [https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size](https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size)
- [https://github.com/vllm-project/vllm](https://github.com/vllm-project/vllm)
- [https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv\_transfer/kv\_connector/utils.py#L569-L573](https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)