CVE-2026-94622 vllm-project CVE debrief

Who should care

Defenders responsible for vLLM deployments, including operators, platform administrators, vulnerability management teams, and security teams, should assess exposure to this denial of service vulnerability and prioritize verification and potential remediation to minimize potential impact on system availability.

Why it matters

Defenders should prioritize verifying exposure of vLLM deployments to this denial of service vulnerability and assess the impact of potential exploitation on their systems.

• Potential denial of service due to decode engine termination
• Potential impact on system availability due to routed requests failing

Technical summary

The vulnerability exists in the NIXL connector's metadata handling for prefill/decode disaggregated deployments in vLLM versions through 0.29.0. An attacker 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. This denial of service vulnerability can impact system availability and defenders should prioritize verifying exposure and assessing potential impact.

Defensive priority

Defenders should prioritize verifying exposure of vLLM deployments to this denial of service vulnerability and assess the impact of potential exploitation on their systems.

Recommended defensive actions

• Verify vLLM deployments for exposure to this denial of service vulnerability
• Assess the impact of potential exploitation on systems
• Apply patches or mitigations as recommended by the vendor
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify vLLM deployments for exposure, assess potential impact, and apply patches or mitigations as recommended. Evidence is limited to public CVE and NVD information; further verification is required to confirm affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.