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.
Affected products
vllm: vllm
References4
- github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437… Vendor Advisory
- github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437… Vendor Advisory
- github.com/vllm-project/vllm/commit/b997071ec493765abbed990c658… Patch
- github.com/vllm-project/vllm/pull/45510 Issue TrackingPatch
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 45 · as of 15 November 2026
- CWE
- CWE-400CWE-770
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.