CVE-2026-114055: vLLM 0.7.3 before 0.31.0 DoS via Unvalidated mm_processor_kwargs

Q: Which deployments are exposed?

vLLM deployments running versions from 0.7.3 up to, but not including, 0.31.0 are affected when remote clients can submit requests that include multimodal processor parameters. The issue can exhaust memory and terminate a shared server.

Q: Does exploitation require authentication or user interaction?

No. The listed vector is network-accessible, with low attack complexity, no privileges required, and no user interaction required.

Q: What should be prioritized for remediation?

Upgrade affected vLLM installations to version 0.31.0 or later. The vulnerable behavior involves per-request mm_processor_kwargs that can control values such as image size, patch count, crop count, and frame count.

Published Oct 21, 2026

Updated

vLLM from 0.7.3 before 0.31.0 contains an uncontrolled resource consumption vulnerability that allows remote clients to control multimodal processor parameters by supplying per-request mmprocessorkwargs. Attackers can set large image size, patch count, crop count, or frame count values in Isaac, InternVL, H2OVL, and other processors to exhaust memory and terminate the shared server.

Affected Software

1 affected component

vllm vllm>=0.7.3<0.31.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade vLLM to a version that resolves this vulnerability.
Fixed in 0.31.0

Event History

Oct 21, 2026

CVE Published

via MITRE·12:36 AM

Data Sourced

via MITRE·12:36 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are exposed?

vLLM deployments running versions from 0.7.3 up to, but not including, 0.31.0 are affected when remote clients can submit requests that include multimodal processor parameters. The issue can exhaust memory and terminate a shared server.

Does exploitation require authentication or user interaction?

No. The listed vector is network-accessible, with low attack complexity, no privileges required, and no user interaction required.

What should be prioritized for remediation?

Upgrade affected vLLM installations to version 0.31.0 or later. The vulnerable behavior involves per-request mm_processor_kwargs that can control values such as image size, patch count, crop count, and frame count.

CVE-2026-114055: vLLM 0.7.3 before 0.31.0 DoS via Unvalidated mm_processor_kwargs

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed?

Does exploitation require authentication or user interaction?

What should be prioritized for remediation?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed?

Does exploitation require authentication or user interaction?

What should be prioritized for remediation?