Vulnerability Description
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vllm | Vllm | <= 0.29.0 |
Related Weaknesses (CWE)
References
- https://github.com/vllm-project/vllmProduct
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kProduct
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kProduct
- https://github.com/vllm-project/vllm/pull/51137Issue TrackingPatch
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-uThird Party Advisory
FAQ
What is CVE-2026-94626?
CVE-2026-94626 is a vulnerability with a CVSS score of 7.5 (HIGH). vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbit...
How severe is CVE-2026-94626?
CVE-2026-94626 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-94626?
Check the references section above for vendor advisories and patch information. Affected products include: Vllm Vllm.