vLLM: VLLM versions through 0.29.0 contain a denial of service vulnerability in the NIXL connector's…
vLLM
More for vLLM RSS feed for vLLM
- Severity
- High, CVSS 7.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Record
- CVE-2026-94622
- Affects
- vLLM
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- September 21, 2026
- Source last modified
- September 29, 2026
Description
vLLM versions through 0.29.0 contain a denial of service vulnerability in the NIXL connector's metadata handling for prefill/decode disaggregated deployments. Attackers can send requests with incomplete kv_transfer_params dictionary entries to trigger an uncaught KeyError in EngineCore scheduling, causing the decode engine to terminate and making all routed requests fail until manual restart.
Description quoted from the NVD record.
Who is affected
This flaw affects vLLM, a server program that runs AI language models so other apps can send them questions and get answers. It affects versions through 0.29.0, but only in setups that split the work across two separate groups of servers: one that first reads each incoming request and one that then writes the answer. The problem is in the NIXL connector, the part that passes information between those two groups. An attacker can send specially shaped requests that make the answer-writing part shut down, so every request sent to it fails until someone restarts it by hand. This flaw is rated High.
What to do
- The person who installed or runs vLLM for your organization should act on this, or the IT provider or vendor who manages it for you.
- Ask them whether your setup splits the work across two groups of servers and uses the NIXL connector. Only that kind of setup is affected.
- No fixed version is named for this flaw yet, so check the vendor advisory linked on this page for a fixed release, and install it as soon as it is available.
- If an IT provider or vendor runs vLLM for you, send them this advisory and ask when the update will be done.
Analysis written from the source record as of September 29, 2026 and reviewed before publishing.