vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.)
CVE-2026-114055
Summary API clients can supply arbitrary mmprocessorkwargs per request. vLLM forwards these values through the multimodal rendering and processing pipeline to Hugging Face and custom image/video processor constructors and calls. Resource-sensitive values such as image size, patch size, patch count, crop count, or frame count can therefore be controlled by a remote client. For processors that upscale inputs, a single request can force an allocation large enough to terminate the API server or worker with an out-of-memory condition. Affected Components The per-request field was introduced in commit 041e29471671a3d43afedb6a749421d56ef4d3e7 and first shipped in v0.7.3. The generic forwarding path remains present in current main. The Isaac path is a concrete high-amplification example: ChatCompletionRequest.mmprocessorkwargs OnlineRenderer request extras MMProcessorInputs.hfprocessormmkwargs BaseMultiModalProcessor.info.gethfprocessor(hfprocessormmkwargs) IsaacProcessingInfo.getimageprocessor(kwargs) IsaacImageProcessor(kwargs) processvisionforpatches() Equivalent constructor forwarding exists in InternVL-derived processors, H2OVL, Step3VL, NemotronVL, and other multimodal processors.…
Part of the AI stack
This affects vLLM, in Inference & serving.
Assessment
- CVSS
- 7.5 (v3.1)
- Severity
- High
- EPSS
- 0.0042% chance of exploitation in the next 30 days
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 23 October 2026
- Last updated
- 23 October 2026
- Affected
- pip · vllm
- Weakness
- CWE-400
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
At the source
References
- https://github.com/vllm-project/vllm/security/advisories/GHSA-gx7p-2j49-hfq4
- https://nvd.nist.gov/vuln/detail/CVE-2026-114055
- https://github.com/vllm-project/vllm/pull/58830
- https://github.com/vllm-project/vllm/commit/31f2e70cd3e403aaa471fb7fe3d33a7207aaf3cc
- https://github.com/vllm-project/vllm/releases/tag/v0.31.0
- https://www.vulncheck.com/advisories/vllm-0.7.3-before-0.31.0-dos-via-unvalidated-mm-processor-kwargs
- https://github.com/advisories/GHSA-gx7p-2j49-hfq4
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-114055