Summary
CVE-2026-116177 is an uncontrolled resource consumption (CWE-400) denial-of-service vulnerability in vLLM. It affects the Nemotron-VL image processors. An unauthenticated remote attacker can send a crafted image that exhausts memory and disrupts service for other users. The CVSS v4.0 score is 8.7 (High).
Technical details
- Root cause: The Nemotron-VL image processors set Pillow’s
Image.MAX_IMAGE_PIXELStoNoneat module load time. This disables Pillow’s decompression-bomb protection for the whole process. - Trigger conditions: The vLLM process has imported a Nemotron-VL processor module. The attacker can reach the
/v1/chat/completionsendpoint. - Attack vector: Network, with no authentication or user interaction. The attacker submits a small, highly compressed image that decodes into a very large pixel buffer.
- Impact: Memory exhaustion and out-of-memory conditions, which deny service to legitimate users. The advisory reports no confidentiality or integrity impact.
Affected software
- vLLM versions 0.10.2 up to, but not including, 0.25.0, as stated in the CVE record.
- Note: the GitHub advisory page lists the affected range differently. Treat all versions before 0.25.0 that use Nemotron-VL processors as potentially affected, and verify against the vendor advisory.
Severity
- CVSS v4.0: 8.7 (High) –
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 - CVSS v3.1: 7.5 (High) –
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Mitigation and recommended actions
- Immediate: Upgrade vLLM to 0.25.0 or later. The fix removes the module-level
Image.MAX_IMAGE_PIXELS = Noneassignments and adds a decoded pixel-count limit to the shared image loader. The limit is configurable through theVLLM_MAX_IMAGE_PIXELSenvironment variable. - If you cannot patch: The advisory lists no official workarounds. As general hardening, restrict network access to the vLLM API to trusted clients and require authentication in front of it.

