CVE-2026-55646: CWE-400: Uncontrolled Resource Consumption in vllm-project vllm
vLLM is an inference and serving engine for large language models. From 0.22.0 to 0.23.0, the /v1/audio/transcriptions and /v1/audio/translations routes call request.file.read() to fully materialize an uploaded audio file into memory before vLLM checks the documented VLLM_MAX_AUDIO_CLIP_FILESIZE_MB compressed upload size limit (default 25 MB) later in the speech-to-text preprocessing step, so an API caller who can reach those routes can submit an oversized multipart upload and cause vLLM to allocate memory proportional to the uploaded file size before the request is rejected as too large, creating memory pressure or terminating the process depending on deployment resource limits. This issue is fixed in version 0.24.0.
AI Analysis
Technical Summary
The vLLM inference and serving engine for large language models has an uncontrolled resource consumption vulnerability (CWE-400) in versions 0.22.0 through 0.23.0. Specifically, the /v1/audio/transcriptions and /v1/audio/translations endpoints call request.file.read() to fully load uploaded audio files into memory before enforcing the documented maximum compressed upload size limit (VLLM_MAX_AUDIO_CLIP_FILESIZE_MB, default 25 MB). This allows an attacker with access to these routes to submit oversized multipart uploads that cause vLLM to allocate memory proportional to the file size before rejecting the request, resulting in memory pressure or process termination depending on deployment resource limits. The vulnerability is addressed in vLLM version 0.24.0.
Potential Impact
An attacker able to access the affected API routes can cause excessive memory consumption by uploading large audio files, leading to denial of service through memory exhaustion or process termination. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Upgrade to vLLM version 0.24.0 or later, where this issue is fixed. Until then, restrict access to the affected API routes or implement external upload size checks to prevent oversized uploads from reaching the service. Patch status is confirmed fixed in 0.24.0.
CVE-2026-55646: CWE-400: Uncontrolled Resource Consumption in vllm-project vllm
Description
vLLM is an inference and serving engine for large language models. From 0.22.0 to 0.23.0, the /v1/audio/transcriptions and /v1/audio/translations routes call request.file.read() to fully materialize an uploaded audio file into memory before vLLM checks the documented VLLM_MAX_AUDIO_CLIP_FILESIZE_MB compressed upload size limit (default 25 MB) later in the speech-to-text preprocessing step, so an API caller who can reach those routes can submit an oversized multipart upload and cause vLLM to allocate memory proportional to the uploaded file size before the request is rejected as too large, creating memory pressure or terminating the process depending on deployment resource limits. This issue is fixed in version 0.24.0.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/vllm-project/vllmRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vLLM inference and serving engine for large language models has an uncontrolled resource consumption vulnerability (CWE-400) in versions 0.22.0 through 0.23.0. Specifically, the /v1/audio/transcriptions and /v1/audio/translations endpoints call request.file.read() to fully load uploaded audio files into memory before enforcing the documented maximum compressed upload size limit (VLLM_MAX_AUDIO_CLIP_FILESIZE_MB, default 25 MB). This allows an attacker with access to these routes to submit oversized multipart uploads that cause vLLM to allocate memory proportional to the file size before rejecting the request, resulting in memory pressure or process termination depending on deployment resource limits. The vulnerability is addressed in vLLM version 0.24.0.
Potential Impact
An attacker able to access the affected API routes can cause excessive memory consumption by uploading large audio files, leading to denial of service through memory exhaustion or process termination. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Upgrade to vLLM version 0.24.0 or later, where this issue is fixed. Until then, restrict access to the affected API routes or implement external upload size checks to prevent oversized uploads from reaching the service. Patch status is confirmed fixed in 0.24.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T23:52:12.058Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4c076a27e9c7971920cc18
Added to database: 07/06/2026, 19:52:10 UTC
Last enriched: 07/06/2026, 20:06:53 UTC
Last updated: 07/06/2026, 22:19:37 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.