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.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://github.com/vllm-project/vllm/commit/b997071ec493765abbed990c65843ed05e4708a8 Patch
- https://github.com/vllm-project/vllm/pull/45510 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437-67m2 Vendor Advisory
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437-67m2 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · vllmNVD modified 2026-10-25 20:10
Affected (CPE criteria) 1
cpe:2.3:a:vllm:vllm:*:*:*:*:*:*:*:*
References 4
- https://github.com/vllm-project/vllm/commit/b997071ec493765abbed990c65843ed05e4708a8 Patch
- https://github.com/vllm-project/vllm/pull/45510 Issue Tracking, Patch
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437-67m2 Vendor Advisory
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437-67m2 Vendor Advisory