KEVWire

Security intelligence, with context.

Response snapshot Oct 26, 2026, 23:07 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-114055

vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.)

API clients can supply arbitrary `mm_processor_kwargs` per request. vLLM forwards these values through the multimodal rendering and processing pipeline to Hugging Face and custom image/video processor constructors and calls.

At a glance

Exploited
Not known
Severity
7.5 High (CVSS 3.1)
Chance of exploitation
0.4% in the next 30 days
Sources
2 independent sources

What to do

GitHub lists first patched versions: vllm: 0.31.0. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-gx7p-2j49-hfq4 (opens a new tab)

What happened

## Summary

API clients can supply arbitrary `mm_processor_kwargs` 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

Continue reading

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.mm_processor_kwargs` - `OnlineRenderer` request extras - `MMProcessorInputs.hf_processor_mm_kwargs` - `BaseMultiModalProcessor.info.get_hf_processor(**hf_processor_mm_kwargs)` - `IsaacProcessingInfo.get_image_processor(**kwargs)` - `IsaacImageProcessor(**kwargs)` - `process_vision_for_patches()`

Equivalent constructor forwarding exists in InternVL-derived processors, H2OVL, Step3VL, NemotronVL, and other multimodal processors. The issue is at the shared remote-input boundary and is not limited to a fixed model list.

## Impact

- **Availability:** one request can exhaust CPU or GPU memory and terminate a shared service process. - **Scope:** all users of the affected service instance lose availability. - **Authentication:** vLLM's API key is optional, so deployments without an external authentication layer are remotely reachable without privileges.

## Remediation

Reject non-empty per-request `mm_processor_kwargs` at every API-server request schema by default. Operators serving only trusted clients can explicitly opt in to the existing override behavior. Server-level `--mm-processor-kwargs` and offline `LLM` overrides remain available.

This shared boundary covers current and future multimodal processors instead of maintaining a model-specific list or a denylist that can miss custom processor arguments.

A patch for this was merged here: https://github.com/vllm-project/vllm/pull/58830

Affected package ranges reported by GitHub: vllm: >= 0.7.3, < 0.31.0

Scores and how they were measured

CVSS base severity

7.5

Version 3.1As of

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.4%

Scored Percentile 36.0%

Model and measurement source (opens a new tab)

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-gx7p-2j49-hfq4 (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-gx7p-2j49-hfq4, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  3. Primary source

    NVD CVE-2026-114055 (opens a new tab)

    NVD record: description, CVSS (the CNA score is preferred), affected products, and publication date. Not evidence of exploitation.

    Published Checked

  4. Primary source

    NVD CVE API 2.0 (opens a new tab)

    The NVD API page that supplied this CVE record.

    Published Date not suppliedChecked

  5. Primary source

    FIRST measured EPSS score (opens a new tab)

    Measured EPSS probability and percentile for CVE-2026-114055, scored 2026-10-26. This is a model estimate, not proof of exposure.

    Published Checked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 23). vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.) (CVE-2026-114055). https://kevwire.com/record/CVE-2026-114055

MLA

"vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.) (CVE-2026-114055)." KEVWire, 23 Oct. 2026, kevwire.com/record/CVE-2026-114055.

Chicago

KEVWire. "vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.) (CVE-2026-114055)." Last modified October 23, 2026. https://kevwire.com/record/CVE-2026-114055.

Evidence summary (plain text)

vLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.) (Oct 23, 2026).
API clients can supply arbitrary `mm_processor_kwargs` 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.
CVSS 7.5 (version 3.1; evidence as of Oct 23, 2026; https://github.com/advisories/GHSA-gx7p-2j49-hfq4).
EPSS 0.4% for the following 30 days, scored Oct 26, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-114055&date=2026-10-26).
Sources:
GitHub-reviewed advisory GHSA-gx7p-2j49-hfq4: https://github.com/advisories/GHSA-gx7p-2j49-hfq4
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
NVD CVE-2026-114055: https://nvd.nist.gov/vuln/detail/CVE-2026-114055
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?pubStartDate=2026-10-12T13:35:55.142Z&pubEndDate=2026-10-26T13:35:55.142Z&resultsPerPage=500&startIndex=7500
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-114055&date=2026-10-26
Record ID: CVE-2026-114055.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 26, 2026, 19:40 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail