CVE-2026-73559 vllm-project CVE debrief

Who should care

Defenders responsible for large language model serving infrastructure, API security, and system resource management should assess exposure and apply the patch. They should also monitor API usage and system resource utilization to prevent potential exploitation. This includes verifying the version of vLLM in use, implementing rate limiting or other controls, and reviewing compensating controls for exposed systems.

Why it matters

CVE-2026-73559 is a vulnerability in vLLM that allows an authenticated API client to exhaust system resources. Defenders should verify exposure, apply the patch, and monitor API usage to prevent potential exploitation.

• Potential for resource exhaustion leading to service unavailability.
• Need for verification of exposure and application of the patch.
• Importance of monitoring API usage and system resource utilization.

Technical summary

The /v1/completions endpoint in vLLM accepts an unbounded list of strings or integers, which can be used to exhaust system resources. An authenticated API client can create multiple engine generators and response slots, leading to potential resource exhaustion. The issue is fixed in version 0.26.0. Defenders should prioritize verifying exposure and applying the patch, as resource exhaustion could impact service availability. Technical details are limited to public CVE and NVD information, which notes that the vulnerability affects vLLM versions 0.19.0 to 0.25.9.

Defensive priority

Defenders should prioritize verifying exposure and applying the patch, as resource exhaustion could impact service availability.

Recommended defensive actions

• Verify if the system uses a vulnerable version of vLLM (0.19.0 to 0.25.9) and apply the patch (version 0.26.0) if necessary.
• Monitor API usage and system resource utilization to detect potential exploitation attempts.
• Implement rate limiting or other controls to prevent abuse of the API.
• 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, affected versions (0.19.0 to 0.25.9), and fixed version (0.26.0). The NVD entry notes that the vulnerability allows an authenticated API client to exhaust CPU, memory, async scheduling capacity, engine request slots, and response buffering with one request. Defenders should verify exposure by checking the version of vLLM in use and apply the patch if necessary. Evidence is limited to public CVE and NVD information.

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.