vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting comple
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| vllm-project | vllm | ≤ 0.29.0 |
affected |
Shenlong is analyzing...
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| vllm-project | vllm | 0 ~ 0.29.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-94624 | 7.5 HIGH | vLLM through 0.29.0 Denial of Service via Unbounded P2P KV Offloading Sessions |
| CVE-2026-94623 | 7.5 HIGH | vLLM through 0.29.0 Denial of Service via NIXL Multi-Prompt Assertion Failure |
| CVE-2026-94626 | 7.5 HIGH | vLLM through 0.29.0 Memory Exhaustion via Unvalidated NIXL tp_size |
| CVE-2026-94622 | 7.5 HIGH | vLLM through 0.29.0 Denial of Service via Incomplete NIXL KV Transfer Metadata |
| CVE-2026-94625 | 5.3 MEDIUM | vLLM through 0.29.0 Resource Exhaustion via Ownerless Mooncake Transfer Placeholders |
No comments yet