vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, vLLM's /v1/audio/transcriptions endpoint limits compressed upload size but not decoded PCM output. A 25MB OPUS file expands to ~14.9GB of float32 PCM at decode time. This vulnerability is fixed in 0.23.1rc0.
CVE-2026-54233
Score 6.5 from GitHub Security Advisory published 2026-06-17. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- 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(high)
- EPSS
- 15.6%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 24, 2026
Advisory Details (2)
Auto-updated Jun 23, 2026OOM Denial of Service via Audio Decompression Bomb · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-6pr9-rp53-2pmc[Security] Fix DoS via audio decompression bomb in speech-to-text endpoint
Fix merged in vllm-project/vllm PR #44970 on 2026-06-09 — awaiting tagged release
https://github.com/vllm-project/vllm/pull/44970Vendor Advisories for CVE-2026-54233(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| pip | vllm | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vllm | 0.0.1 ... 0.9.2 (89 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 65× 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-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 21:46 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 15:15 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 14:25 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 13:38 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 12:51 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 12:03 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 11:12 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
Show 47 moreShow fewer
- 2026-07-09 10:16 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 09:28 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 08:41 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 07:19 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 06:29 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:47 UTCGHSA enrichment
- 2026-07-03 02:45 UTCGHSA enrichment
- 2026-07-02 01:56 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 01:08 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 00:19 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 23:32 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 22:45 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 21:58 UTCGHSA enrichment
- 2026-06-25 21:10 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 20:23 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 19:36 UTCGHSA enrichment
- 2026-06-22 18:48 UTCGHSA enrichment
- 2026-06-21 18:00 UTCGHSA enrichment
- 2026-06-20 17:08 UTCGHSA enrichment
- 2026-06-19 16:21 UTCGHSA enrichment
- 2026-06-18 15:32 UTCGHSA enrichment
- 2026-06-17 14:45 UTCEG score recompute
- 2026-06-17 14:45 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-54233?
When was CVE-2026-54233 disclosed?
Is CVE-2026-54233 actively exploited?
What is the CVSS score of CVE-2026-54233?
How do I remediate CVE-2026-54233?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54233
Is Your Infrastructure Affected by CVE-2026-54233?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.