Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain authenticated chat API access
-
DeliveryCraft tiny highly-compressed audio payload
-
ExploitSubmit via input_audio or audio_url to /v1/chat/completions
-
ExecutionDecoder expands to huge decoded PCM
-
ImpactServer memory exhausted, availability denied
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
|
| Exploitation Conditions | Requires an audio-capable (multimodal) vLLM deployment in the 0.19.0-0.23.x range that accepts audio content parts on /v1/chat/completions, and an attacker able to submit chat completion requests. The specific trigger is an input_audio data URL or an audio_url that routes through MediaConnector.fetch_audio() to AudioMediaIO.load_bytes()/load_file(), which call load_audio(..., sr=None) without passing max_duration_s. Limiting factors: by default API-key authentication is required (hence PR:L); the audio model/path must be enabled; and --allowed-media-domains, media fetch timeouts, and HTTP body limits constrain some audio_url delivery options but do NOT enforce a decoded-PCM duration/sample budget, so input_audio payloads fitting normal request size limits remain exploitable. If chat completions are exposed without authentication, the condition collapses to unauthenticated reachability (PR:N). |
| Impact | This is a medium-severity, availability-only denial-of-service issue (CWE-409 data amplification), and the signals are internally consistent rather than conflicting. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the GHSA-provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) agree: network-reachable, low attack complexity, low privileges required (an authenticated API caller), no user interaction, impacting availability only (VA:H / A:H) with no confidentiality or integrity effect. It is NOT in CISA KEV and there is no public exploit identified at time of analysis - no PoC or exploit-code reference is present in the input (only vendor/VulnCheck advisories). No EPSS score was provided, so statistical exploitation probability cannot be cited; its absence is not evidence of low risk. No SSVC fields were supplied; the only priority signal is the vuln.today Decision label 'this_week', consistent with a real but non-emergency DoS. The PR:L baseline is explicitly a policy choice tied to API-key auth: the advisory states that a deployment exposing chat completions WITHOUT authentication should be assessed at PR:N, which would raise real-world risk. Net: a genuine availability risk worth patching on a near-term schedule, not a confidentiality/RCE emergency; priority rises sharply for unauthenticated-exposed, audio-capable deployments. |
| Exploit ScenarioDerived | An authenticated user of an audio-capable vLLM deployment sends a /v1/chat/completions request containing a small, highly compressed audio payload via input_audio (or an audio_url) that decodes to an enormous PCM buffer. Because AudioMediaIO calls load_audio without the max_duration_s guard, the decoder accumulates the oversized decoded frames before any model-level clip limit applies, exhausting server memory and degrading or denying availability. No public exploit code is identified at time of analysis, though the mechanism is fully described in the vendor advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 25, 2026
Memory exhaustion in vLLM's multimodal chat audio path lets an authenticated API user submit a small compressed audio payload to /v1/chat/completions that decodes into very large PCM data, driving up server memory and degrading or halting availability. Deployments in the >= 0.19.0, < 0.24.0 range that accept audio content parts are affected; the fix in 0.24.0 extends the existing decoded-duration guard to AudioMediaIO, which currently calls load_audio(..., sr=None) with no max_duration_s bound. Exploitation requires a valid API key by default (PR:L) and an audio-capable deployment; no public exploit code was identified at time of analysis, and the issue is a sibling of the already-published speech-to-text decompression-bomb advisory.
RemediationAI
Vendor-released patch: upgrade vLLM to 0.24.0, which per the advisory applies the decoder duration guard inside AudioMediaIO by adding a validated max_duration_s field defaulted to envs.VLLM_MAX_AUDIO_DECODE_DURATION_S and passing it from load_bytes() and load_file() into load_audio(...), while preventing request-level media_io_kwargs["audio"] from disabling or raising the server-side cap; regression coverage was added for AudioMediaIO, MediaConnector.fetch_audio() and chat input_audio/audio_url (advisory: https://github.com/vllm-project/vllm/security/advisories/GHSA-r45p-7qwx-qwjw). On unpatched 0.19.0-0.23.x builds, setting VLLM_MAX_AUDIO_DECODE_DURATION_S does not close this hole because the chat media path never passes the limit, so it is not a substitute for the 0.24.0 upgrade. Compensating measures that the advisory notes reduce some delivery options without enforcing a decoded PCM duration/sample budget: restricting --allowed-media-domains (blocks arbitrary audio_url sources but not input_audio data embedded in the request body), tightening media fetch timeouts, and lowering HTTP body size limits (both constrain payload delivery but do not bound the decoded output); keeping API-key authentication on /v1/chat/completions maintains the PR:L prerequisite, and if chat completions are exposed unauthenticated the issue becomes reachable with PR:N. Where audio chat is not required, disabling the multimodal audio path removes the exposure entirely, at the cost of that feature.
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
CWE-409 (Improper Handling of Highly Compressed Data / data amplification) is the root-cause class: the decoder materializes decoded PCM in memory before any model-level audio clip limits are applied, so a tiny compressed input can amplify into a disproportionately large in-memory buffer. vLLM's earlier fix for the speech-to-text decompression bomb (GHSA-6pr9-rp53-2pmc / CVE-2026-54233) added VLLM_MAX_AUDIO_DECODE_DURATION_S and wired a max_duration_s argument into load_audio(), load_audio_soundfile() and load_audio_pyav(), but that argument defaults to None, so existing callers were left unaffected. The multimodal chat path was one such caller: MediaConnector.fetch_audio() constructs AudioMediaIO, whose load_bytes() and load_file() invoke load_audio(BytesIO(data), sr=None) and load_audio(filepath, sr=None) without the bound, and chat_utils.py routes both input_audio data URLs and audio_url media parts into it. Because the guard is opt-in, the /v1/audio/transcriptions endpoint is protected while /v1/chat/completions audio ingestion is not - an incomplete-fix variant rather than a distinct decoder defect. The decoder itself already supports metadata and decoded-sample duration limits; the chat media path simply never passes the limit, and untrusted request-level media_io_kwargs["audio"] is not prevented from altering the cap.
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:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Authenticated API caller (PR:L) sends a crafted request over the network (AV:N/AC:L/UI:N); impact is availability-only memory exhaustion (A:H), no confidentiality or integrity effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
vLLM from 0.19.0 before 0.24.0 contains a decompression bomb vulnerability because the AudioMediaIO multimodal path calls load_audio without the max_duration_s decoded-duration limit. Authenticated attackers can send small compressed audio via input_audio or audio_url in /v1/chat/completions requests that expands to huge decoded PCM, exhausting server memory.
Technical POC Analysis
CWE-409: Improper Handling of Highly Compressed Data (Data Amplification).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
CVE-2026-116175 is a high-severity availability vulnerability in vLLM's audio processing that allows authenticated API users to exhaust server memory with compressed audio payloads, potentially disrupting AI services. Organizations running affected vLLM versions (0.19.0 to 0.24.0) for multimodal applications should prioritize remediation, as this could impact customer-facing services and internal operations that rely on these AI capabilities.
Apply vendor patch.
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
vLLM 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
Denial of service in the vLLM LLM inference server (all versions prior to 0.24.0) allows a remote client to crash the sh
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
EUVD-2026-109436
GHSA-vchq-p6cc-h35x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB