Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed SGLang audio inference endpoint
-
DeliverySubmit tiny compressed FLAC silence file
-
Exploitload_audio decodes without duration/sample limits
-
ExecutionPCM buffer expands to exhaust memory
-
ImpactWorker memory/CPU starvation denies service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Compression ratio limits
|
| Exploitation Conditions | The target SGLang instance (<=0.5.21) must be deployed serving an audio-capable multimodal model and must accept attacker-supplied audio via the audio_url or audio_data inputs, since load_audio performs no duration or sample-count limiting during decode. Exploitation is otherwise unrestricted: CVSS PR:N/UI:N and the endpoint is typically unauthenticated, so no credentials or user interaction are needed. The principal limiting factor is configuration-based exposure - SGLang deployments that serve only text models, or that place the inference endpoint behind authentication/network restrictions or request-size/resource limits, are not exploitable via this path. |
| Impact | Signals point to a genuine but bounded availability risk. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VA:H, everything else N) scores 8.7 and is internally consistent with the description: a remote, unauthenticated, low-complexity denial-of-service with no confidentiality or integrity impact. My independent CVSS 3.1 mapping yields 7.5 (A:H only), so the headline 8.7 reflects CVSS 4.0's weighting rather than any confidentiality/integrity exposure - this is a pure DoS, not RCE. No EPSS score, SSVC decision, KEV listing, or POC is present in the input, so exploitation likelihood cannot be quantified; per precision rules this is 'no public exploit identified at time of analysis.' The amplification nature (small FLAC silence → massive PCM buffer) makes exploitation cheap and automatable in principle, which raises practical concern, but the absence of any exploitation evidence and the requirement that the target actually expose audio multimodal inference tempers it. Net: a real priority for operators running SGLang audio-serving endpoints exposed to untrusted input, but a lower priority than the 8.7 might suggest for the majority of SGLang deployments that do not accept audio. |
| Exploit ScenarioDerived | An attacker locates an internet-reachable SGLang server configured to serve an audio-capable multimodal model and submits a tiny, highly compressed FLAC file of silence via the audio_url or audio_data input. load_audio decodes it without duration or sample limits, expanding it into an enormous PCM buffer that consumes worker memory and CPU; repeating the request starves the service and denies availability. No public exploit code was identified, but the attack requires no authentication and only low complexity (AV:N/AC:L/PR:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Denial of service in SGLang through 0.5.21: unauthenticated remote attackers can exhaust server memory and CPU by submitting tiny, highly compressed FLAC files (typically pure digital silence) through the audio_url or audio_data inputs of the multimodal audio pipeline, which decodes them into enormous PCM buffers with no duration or sample-count ceiling. The issue is scored 8.7 under CVSS 4.0 (and AV:N/AC:L/PR:N/UI:N/A:H under CVSS 3.1) with availability impact only and no confidentiality or integrity impact, and no public exploit code was identified at time of analysis. Exposure is bounded: only deployments that actually serve an audio-capable multimodal model and accept attacker-supplied audio without authentication, request limits, or resource caps can be driven into memory exhaustion, making this a genuine but configuration-dependent availability risk.
RemediationAI
No vendor-released patch was identified at time of analysis, so the primary action is to track the upstream issue https://github.com/sgl-project/sglang/issues/43708 and the advisory https://www.vulncheck.com/advisories/sglang-through-0.5.21-audio-decompression-amplification-via-load-audio for a fixed release, and upgrade as soon as a version above 0.5.21 is published; do not assume a fix exists until it is tagged. Until then, the most effective control is to enforce limits on the DECODED audio, not the encoded payload: add a wrapper that rejects waveforms exceeding a fixed duration or sample count (for example a few seconds for transcription-style workloads) or refuses inputs whose decoded size exceeds a configured cap, since a raw request-size or upload-byte limit will not help (the malicious FLAC payload is only a few kilobytes). Where such a wrapper cannot be deployed, disable audio ingestion entirely for internet-facing instances - remove audio-capable multimodal models from the served model list or reject requests containing audio_url/audio_data at the reverse proxy - with the obvious trade-off that legitimate audio and audio-from-video features stop working. Additional compensating controls with modest trade-offs: require authentication and network-level restrictions on the inference endpoint (PR:N and UI:N mean anyone who can reach it can trigger this), apply per-request rate limits and concurrency caps to slow the amplification, and run workers inside cgroup memory limits with aggressive OOM handling so an exhausted worker is killed and restarted rather than taking down the host - noting this converts a host outage into repeated worker restarts and transient request failures, not a real fix. Decoder-level hardening (for example capping the total number of decoded samples at the soundfile/ffmpeg call site) is the correct long-term code change and should be contributed or applied as a local patch if you maintain a fork.
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
The root cause is CWE-409 (Improper Handling of Highly Compressed Data), the classic decompression-bomb pattern applied to the audio ingestion path of an LLM serving stack. SGLang's load_audio routine in python/sglang/srt/utils/common.py (referenced at line 1783, with the decode/expansion logic at lines 1801-1803) hands attacker-controlled bytes to a decoder and returns the fully expanded waveform without ever constraining decoded duration or sample count; the same unchecked path is reachable through the video-to-audio extraction helper in python/sglang/srt/multimodal/audio_from_video.py (line 128) and through the request processor in python/sglang/srt/multimodal/processors/base_processor.py (line 996), which is where audio_url and audio_data request fields are handled. FLAC is lossless but exploits its predictor and run-length coding: a stream of samples with identical values (silence) compresses by several orders of magnitude, so a few kilobytes of input can expand into hours of 44.1 kHz stereo PCM - on the order of tens of megabytes per minute of decoded audio - all of which is materialised in the worker process before any model inference occurs. Because decoding is CPU-bound and the buffer is host memory (and potentially device memory when audio embeddings are built), a handful of concurrent requests can push a worker into OOM-kill or sustained CPU saturation, degrading or halting all other sessions served by that process. There is no memory-safety, injection, or information-disclosure component; the entire impact is resource exhaustion.
Know when Sglang 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 audio input with no user interaction drives AV:N/AC:L/PR:N/UI:N; impact is availability-only memory/CPU exhaustion, so C:N/I:N/A:H and scope unchanged.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
SGLang through 0.5.21 contains a decompression amplification vulnerability in load_audio that allows remote attackers to exhaust memory by submitting highly compressed audio decoded without duration or sample limits. Attackers can supply small FLAC-encoded silence files through audio_url or audio_data inputs that expand into massive PCM buffers, exhausting worker memory and CPU for denial of service.
Executive ViewAI
Organizations running SGLang versions through 0.5.21 with exposed audio-capable multimodal inference services face a configuration-dependent availability risk from CVE-2026-109226 (CVSS 8.7). An unauthenticated remote attacker could exhaust server memory and CPU, causing outages for applications that rely on this AI pipeline; no public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis. Leadership should care because the attack requires no credentials and can disrupt services, though impact is limited to availability and only affects deployments that accept untrusted audio without resource limits.
No vendor-released patch identified at time of analysis; implement authentication, strict input validation (limit audio duration/sample count), rate limiting, memory and CPU resource caps, network segmentation, and continuous monitoring for resource exhaustion.
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.
Remote code execution in SGLang (versions up to and including 0.5.15) allows unauthenticated attackers to run arbitrary
SGLang's multimodal generation module deserializes untrusted data with pickle.loads() over an unauthenticated ZMQ broker
SGLang's encoder parallel disaggregation system is vulnerable to unauthenticated RCE through pickle deserialization in t
Unauthenticated remote code execution in SGLang (the LLM/multimodal generation serving runtime) affecting version 5.10 a
Remote code execution in SGLang 0.5.9's /v1/rerank endpoint allows unauthenticated attackers to execute arbitrary code b
Remote code execution in SGLang (versions up to and including 0.5.15) allows attackers to run arbitrary code on the infe
Remote code execution in SGLang AI inference servers allows unauthenticated attackers to run arbitrary code through the
Remote code execution in SGLang (versions ≤ v0.5.15) allows attackers to achieve arbitrary code execution through the op
Unauthenticated remote code execution affects SGLang, an LLM/multimodal inference-serving framework, at version 5.10, wh
Unauthenticated remote code execution in SGLang versions through v0.5.20 arises from unsafe pickle deserialization in th
Unauthenticated remote code execution in SGLang 0.5.11 through 0.5.14 occurs when the multimodal generation runtime is l
Unauthenticated remote code execution in SGLang (versions 0 through 0.5.14) arises when the expert-parallel backup subsy
EUVD-2026-97432
GHSA-h3xf-3226-h48g
NVD
CVE.org
EPSS
Exploit-DB