vLLM up to 0.22.1 OPUS File /v1/audio/transcriptions data amplification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.65 |
Summary
A vulnerability was found in vLLM. It has been classified as problematic. This affects an unknown part of the file /v1/audio/transcriptions of the component OPUS File Handler. Performing a manipulation results in data amplification. This vulnerability is known as CVE-2026-54233. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in vLLM. This affects an unknown code block of the file /v1/audio/transcriptions of the component OPUS File Handler. The manipulation with an unknown input leads to a data amplification vulnerability. CWE is classifying the issue as CWE-409. The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. This is going to have an impact on availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-54233 since 06/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 0.23.1rc0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.7.0
- 0.7.2
- 0.8.0
- 0.8.5
- 0.9.0
- 0.10.1.1
- 0.10.3
- 0.11.1
- 0.12.0
- 0.13.0
- 0.14.0
- 0.14.1
- 0.17.0
- 0.18.0
- 0.19.0
- 0.20.0
- 0.22.0
- 0.22.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Data amplificationCWE: CWE-409 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vLLM 0.23.1rc0
Patch: github.com
Timeline
06/12/2026 CVE reserved06/23/2026 Advisory disclosed
06/23/2026 VulDB entry created
06/23/2026 VulDB entry last update
Sources
Advisory: GHSA-6pr9-rp53-2pmcStatus: Confirmed
CVE: CVE-2026-54233 (🔒)
GCVE (CVE): GCVE-0-2026-54233
GCVE (VulDB): GCVE-100-372825
Entry
Created: 06/23/2026 07:21Changes: 06/23/2026 07:21 (65)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.