CVE-2026-114055 vllm-project CVE debrief

Who should care

Defenders responsible for vLLM deployments, particularly those using versions between 0.7.3 and 0.31.0, should assess exposure and prioritize patching or mitigation. Defenders should also review compensating controls for exposed systems while remediation is scheduled and verified. Additionally, defenders should check relevant monitoring, detection, and logs for exposed assets that need extra review.

Why it matters

CVE-2026-114055 is a denial-of-service vulnerability in the vLLM library, which allows remote clients to cause an out-of-memory condition by supplying arbitrary `mm_processor_kwargs` per request. Defenders should prioritize verifying exposure of affected versions and applying the patch or mitigating the vulnerability.

• Potential out-of-memory condition leading to denial-of-service
• Exposure of vLLM versions between 0.7.3 and 0.31.0 requires verification and patching
• Remote clients can control resource-sensitive values, potentially leading to security issues

Technical summary

The vulnerability is caused by the forwarding of unvalidated `mm_processor_kwargs` to Hugging Face and custom image/video processor constructors and calls. This allows remote clients to control resource-sensitive values such as image size, patch size, patch count, crop count, or frame count, potentially leading to an out-of-memory condition. The issue was introduced in version 0.7.3 and fixed in version 0.31.0. Defenders should prioritize verifying exposure of affected versions and apply the patch or mitigating the vulnerability through compensating controls. The vulnerability can be mitigated by

Defensive priority

Defenders should prioritize verifying exposure of vLLM versions between 0.7.3 and 0.31.0 and applying the patch or mitigating the vulnerability through compensating controls.

Recommended defensive actions

• Verify exposure of vLLM versions between 0.7.3 and 0.31.0
• Apply the patch by updating to version 0.31.0 or later
• Implement compensating controls to mitigate the vulnerability
• Monitor for suspicious activity and exception tracking
• 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

Evidence notes

The vulnerability is caused by the forwarding of unvalidated `mm_processor_kwargs` to Hugging Face and custom image/video processor constructors and calls. This allows remote clients to control resource-sensitive values such as image size, patch size, patch count, crop count, or frame count, potentially leading to an out-of-memory condition.

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.