CVE-2026-94625 vllm-project CVE debrief

Who should care

Defenders responsible for vLLM deployments, operators of affected platforms, vulnerability management teams, and security teams should assess exposure to this vulnerability and prioritize verification and remediation efforts. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is

Why it matters

CVE-2026-94625 is a resource exhaustion vulnerability in vLLM through version 0.29.0. Defenders should prioritize verifying the version of vLLM in use and assessing exposure to this vulnerability. If vulnerable, they should apply patches or mitigations as available.

• Valid requests may be delayed by up to 480 seconds.
• Health checks may continue returning success despite the vulnerability.
• The vulnerability requires verification of vLLM versions and exposure.
• Remediation priority is high for affected deployments.

Technical summary

The vulnerability is caused by rejected prefill requests creating ownerless transfer placeholders that are never reclaimed in vLLM through version 0.29.0. This can lead to valid requests being delayed by up to 480 seconds while health checks continue returning success. The issue requires verification of vLLM versions and exposure, and remediation priority is high for affected deployments. Defenders should prioritize verifying the version of vLLM in use and assessing exposure to this vulnerability. If vulnerable, they should apply patches or mitigations as available.

Defensive priority

Defenders should prioritize verifying the version of vLLM in use and assessing exposure to this vulnerability. If vulnerable, they should apply patches or mitigations as available.

Recommended defensive actions

• Verify the version of vLLM in use and assess exposure to this vulnerability.
• Apply patches or mitigations as available.
• Monitor for rejected prefill requests and ownerless transfer placeholders.
• Review health checks for potential false positives.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and affected versions. However, the corpus does not establish exploitation or impact, and remediation requires verification from the supplied official sources.

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.