vLLM is an inference and serving engine for large language models. Prior to 0.24.0, the input_audio handling path for /v1/chat/completions calls AudioMediaIO.load_bytes or AudioMediaIO.load_file without passing VLLM_MAX_AUDIO_DECODE_DURATION_S to the shared audio decoder. An unauthenticated client can therefore submit a small compressed audio input that expands into a very large float32 PCM allocation, bypassing the duration guard already used by /v1/audio/transcriptions and causing an out-of-memory worker crash. Inline data URLs reach this path without being bounded by VLLM_AUDIO_FETCH_TIMEOUT. The issue affects deployments serving an audio-capable model, and authentication changes only the deployment-specific reachability. This issue is fixed in version 0.24.0.
CVE-2026-57173
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (4)
Auto-updated Sep 16, 2026v0.24.0
Patch available: vllm-project/vllm v0.24.0
https://github.com/vllm-project/vllm/releases/tag/v0.24.0commit 3d20275bb4d4 (vllm-project/vllm)
Fix landed in vllm-project/vllm commit 3d20275bb4d4 — awaiting tagged release
https://github.com/vllm-project/vllm/commit/3d20275bb4d434f53055c3c0b645fd8bb072965efix(security): enforce audio decode duration limit in chat completions path
Fix merged in vllm-project/vllm PR #45908 on 2026-06-17 — awaiting tagged release
https://github.com/vllm-project/vllm/pull/45908Unauthenticated audio decompression-bomb DoS in /v1/chat/completions: VLLM_MAX_AUDIO_DECODE_DURATION_S guard not wired into the chat audio path (sibling of CVE-2026-5497) · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-hcwq-8wjf-3gcrVendor Advisories for CVE-2026-57173(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vllm | 0.0.1 ... 0.9.2 (89 versions) | 0.24.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:32 UTCEG score recompute
- 2026-09-18 18:15 UTCEG score recompute
- 2026-09-18 14:15 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 17:29 UTCEG score recompute
- 2026-09-16 16:46 UTCEG score recompute
- 2026-09-16 16:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-57173?
When was CVE-2026-57173 disclosed?
Is CVE-2026-57173 actively exploited?
What is the CVSS score of CVE-2026-57173?
How do I remediate CVE-2026-57173?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57173
Is Your Infrastructure Affected by CVE-2026-57173?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.