# CVE-2026-54233: vLLM: OOM Denial of Service via Audio Decompression Bomb

> Attackers can cause denial of service in vLLM by uploading small audio files that expand into massive memory usage during decoding.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-6pr9-rp53-2pmc, MINI-77wq-q45h-v222, MINI-ffxm-53gj-7fj8, MINI-v9fq-hhgm-m8m6, PYSEC-2026-3404

## What is CVE-2026-54233?

CVE-2026-54233 is a medium-severity denial of service vulnerability in Vllm Vllm, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-54233?

3 open source packages ship an affected version, including vllm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vllm` | PyPI | All versions to 0.23.0 | None |
| `vllm` | PyPI | All versions | 0.24.0 |
| `vllm` | PyPI | All versions | 0.24.0 |

Products: Vllm Vllm.

## How do I fix CVE-2026-54233?

Upgrade vllm to 0.24.0 or later.

## Is CVE-2026-54233 being exploited?

There is no known exploitation of CVE-2026-54233 in the wild and no public exploit code.

## Other vulnerabilities in Vllm Vllm

- [CVE-2025-32444](https://insights.sbomify.com/CVE-2025-32444/): vLLM Vulnerable to Remote Code Execution via Mooncake Integration (critical 10.0)
- [CVE-2026-22778](https://insights.sbomify.com/CVE-2026-22778/): vLLM leaks a heap address when PIL throws an error (critical 9.8)
- [CVE-2025-47277](https://insights.sbomify.com/CVE-2025-47277/): vLLM Allows Remote Code Execution via PyNcclPipe Communication Service (critical 9.8)
- [CVE-2024-11041](https://insights.sbomify.com/CVE-2024-11041/): Remote Code Execution in vllm-project/vllm (critical 9.8)
- [CVE-2026-48746](https://insights.sbomify.com/CVE-2026-48746/): vLLM: OpenAI auth bypass (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54233 and fix it if it is affected.

What it is: CVE-2026-54233 is a medium-severity denial of service vulnerability in Vllm Vllm, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54233 in the wild and no public exploit code.

Affected packages and fixed versions:
- vllm (PyPI): affected all versions up to 0.23.0; no fix listed
- vllm (PyPI): affected all versions; fixed in 0.24.0
- vllm (PyPI): affected all versions; fixed in 0.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54233/ (Markdown: https://insights.sbomify.com/CVE-2026-54233/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54233
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54233
- OSV: https://osv.dev/vulnerability/CVE-2026-54233

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54233/
Summaries are generated and may contain mistakes; the official description above is the record.