Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed vLLM inference endpoint
-
DeliveryCraft request with malicious mm_processor_kwargs
-
ExploitSet oversized image/patch/crop/frame values
-
ExecutionProcessor allocates excessive memory
-
ImpactHost memory exhausted, server terminated
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target vLLM instance (versions 0.7.3 up to but not including 0.31.0) is serving a multimodal model using an affected processor - the advisory names Isaac, InternVL, and H2OVL among others - and that the deployment accepts client-supplied per-request mm_processor_kwargs without validation or restriction. The attacker needs only network reachability to the inference API; no authentication (PR:N) and no user interaction (UI:N) are required. Limiting factors: text-only models and deployments that disable, hard-code, or sanitize mm_processor_kwargs are not exploitable, and the impact is confined to denial of service (server termination) with no data compromise, so the realistic risk is highest for multi-tenant or publicly exposed multimodal serving setups. |
| Impact | This is a legitimate availability-focused priority within AI/ML serving environments, though not a top-tier emergency across the broader infrastructure landscape. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms a remote, unauthenticated, low-complexity attack with no user interaction, and impact is cleanly scoped to availability (VA:H) with no confidentiality or integrity effect - consistent with the CWE-400 uncontrolled-resource-consumption classification and the description's account of memory exhaustion crashing the shared server. The reported 8.7 score is high but reflects a pure denial-of-service outcome, not code execution or data exposure, so it should not be equated with a critical RCE. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data; per the precision rule this means no public exploit is identified at time of analysis, and exploitation is neither confirmed nor demonstrated. The practical risk is real for any multi-tenant or internet-exposed vLLM deployment serving affected multimodal models, because a single crafted request can terminate a server shared by many users, but the absence of exploitation signals (EPSS/KEV/POC) suggests this is a hardening priority rather than an actively-attacked flaw. Key missing data: no EPSS probability was supplied to gauge likelihood, and no SSVC decision metadata (automatable/exploitation status) was provided - these should be consulted before final prioritization. |
| Exploit ScenarioDerived | An attacker with network access to a vLLM endpoint serving a multimodal model (e.g., InternVL, Isaac, or H2OVL) sends an inference request that includes per-request mm_processor_kwargs with oversized values such as an extreme image size, patch count, crop count, or frame count. The multimodal processor honors these client-controlled parameters and allocates vast amounts of memory, exhausting host resources and terminating the shared server for all tenants. No public exploit code is identified at time of analysis, but the attack is unauthenticated and low-complexity, requiring only a single crafted API request. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Remote unauthenticated memory exhaustion in vLLM 0.7.3 through versions before 0.31.0 allows clients to terminate shared multimodal inference servers by supplying oversized per-request mm_processor_kwargs, such as large image sizes, patch counts, crop counts, or frame counts, to processors including Isaac, InternVL, and H2OVL. Deployments are exposed when they serve a multimodal model and accept client-controlled mm_processor_kwargs without validation; text-only models and hardened configurations that disable or clamp these parameters are not affected. No public exploit was identified at time of analysis, and the impact is availability-only, with the highest practical risk for multi-tenant or internet-exposed inference APIs.
RemediationAI
Vendor-released patch: upgrade vLLM to 0.31.0 or later, which is the first fixed version per the advisory at https://github.com/vllm-project/vllm/security/advisories/GHSA-gx7p-2j49-hfq4. If immediate upgrade is not possible, restrict network reachability to the inference API through an authenticating gateway or private network because the issue is unauthenticated and remote; the trade-off is reduced accessibility for legitimate clients. Disable client-supplied per-request mm_processor_kwargs and hard-code conservative image size, patch count, crop count, and frame count limits where the serving configuration permits, accepting reduced flexibility for multimodal callers. Add request-size and rate limits at the reverse proxy and run vLLM workers under memory limits with restart supervision, understanding that memory limits convert global server termination into per-worker failure but do not remove the root cause. The VulnCheck advisory at https://www.vulncheck.com/advisories/vllm-0.7.3-before-0.31.0-dos-via-unvalidated-mm-processor-kwargs provides additional context.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
vLLM is a high-throughput inference and serving engine for large language and multimodal models, commonly exposed through an OpenAI-compatible HTTP API. Multimodal processors convert images and video into model-ready tensors and metadata; the per-request mm_processor_kwargs field lets callers override processor settings such as image size, patch count, crop count, and frame count. The root cause is CWE-400 Uncontrolled Resource Consumption: the server does not adequately bound or validate these client-supplied values, so crafted requests can force excessive allocation and trigger memory exhaustion that terminates the shared server process. The vulnerability affects vLLM packages tracked as cpe:2.3:a:vllm-project:vllm, with the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H indicating a remote, unauthenticated denial of service with no confidentiality or integrity impact. The supplied CVSS:4.0 vector similarly records PR:N and high availability impact, consistent with the independent assessment.
Know when Vllm gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Remote unauthenticated single-request attack (AV:N/AC:L/PR:N/UI:N) causing only server crash, so A:H with C:N/I:N and no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
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 mm_processor_kwargs. 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.
Technical POC Analysis
CWE-400 (Uncontrolled Resource Consumption).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
vLLM multimodal inference deployments running versions 0.7.3 up to but not including 0.31.0 can be terminated by crafted requests that exhaust server memory, disrupting shared AI inference services. Leadership should care because internet-exposed or multi-tenant inference APIs may lose availability for multiple teams or customers, although the impact is availability-only and no public exploit was identified at time of analysis.
No vendor-released patch identified at time of analysis; interim mitigations include disabling or clamping client-controlled mm_processor_kwargs (image sizes, patch counts, crop counts, frame counts), rejecting oversized requests at the API gateway, rate limiting, restricting multimodal endpoints to trusted clients, isolating shared inference servers, and monitoring memory exhaustion and service restarts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Related Vulnerabilities in vLLM Cache and Resource Consumption Vulnerabilities
View all 7vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Rated critical severity (CVSS 10.0
vllm-project vllm version v0.6.2 contains a vulnerability in the MessageQueue.dequeue() API function. Rated critical sev
Information exposure in vLLM inference engine versions 0.8.3 to before 0.14.1. Invalid image requests to the multimodal
Timing-based API key recovery in vLLM before 0.11.0rc2 can let remote attackers bypass bearer-token authentication on de
vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Rated high severity (CVSS 7.5), th
vLLM before version 0.14.1 contains a server-side request forgery vulnerability in the MediaConnector class where incons
Out-of-memory worker crashes in vLLM can be induced by a single small compressed audio payload submitted to the /v1/chat
vLLM is a high-throughput and memory-efficient inference and serving engine for LLMs. Rated medium severity (CVSS 6.5),
GPU memory exhaustion in vLLM versions prior to 0.28.0 lets an attacker with low-privileged API access (PR:L in the CVSS
Multimodal inference requests to vLLM deployments running versions prior to 0.28.0 can trigger a process-level assertion
Uncontrolled resource consumption in vLLM's OpenAI-compatible completions endpoint allows any authenticated API client t
Vllm versions up to 0.12.0 is affected by allocation of resources without limits or throttling (CVSS 6.5).
EUVD-2026-107006
GHSA-3cgq-c484-rx5j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB