Summary
vLLM: Speech-to-text upload size limit is enforced after full UploadFile read
Current-head vLLM documents VLLM_MAX_AUDIO_CLIP_FILESIZE_MB as the maximum audio file size accepted by the speech-to-text APIs. The default is 25 MB. vllm/envs.py also describes files larger than this value as rejected.
The /v1/audio/transcriptions and /v1/audio/translations routes call await request.file.read() before vLLM checks that limit. In FastAPI and Starlette, UploadFile.read() returns bytes from the uploaded file object; when called without a size argument, the route materializes the remaining file contents. vLLM then performs the compressed file-size check later in _preprocess_speech_to_text() against the already-created bytes object.
As a result, the documented compressed audio file-size limit does not bound the memory allocated by vLLM endpoint code before validation. An oversized multipart upload can cause vLLM to allocate memory proportional to the uploaded file size before rejecting the request as too large.
This is distinct from GHSA-6pr9-rp53-2pmc, which covered decoded PCM expansion after compressed input was accepted. This report covers compressed upload materialization before compressed-size validation.
Technical Details
The upload routes perform an unbounded read before vLLM checks the documented compressed audio file-size limit:
vllm/entrypoints/speech_to_text/transcription/api_router.py:audio_data = await request.file.read()vllm/entrypoints/speech_to_text/translation/api_router.py:audio_data = await request.file.read()vllm/entrypoints/speech_to_text/base/serving.pylater checks:if len(audio_data) / 1024**2 > self.max_audio_filesize_mb
There is no route-level check of request.file.size, Content-Length, a bounded read(max_bytes + 1), or a streaming copy that stops at the configured limit before the full file is materialized.
This does not appear to be intended behavior. vLLM's security guide treats request-controlled resource use as a security boundary: for example, requests that exceed VLLM_MAX_N_SEQUENCES are rejected before reaching the engine. The speech-to-text upload limit is documented in the same spirit as an API enforced limit, but the first vLLM check happens after the over-limit upload has already been copied into a bytes object.
Resources
- vLLM security policy:
https://github.com/vllm-project/vllm/security/policy - vLLM speech-to-text docs:
https://docs.vllm.ai/en/latest/serving/online_serving/speech_to_text/ - vLLM security guide, request parameter resource limits:
https://docs.vllm.ai/en/latest/usage/security/ - vLLM vulnerability management docs:
https://docs.vllm.ai/en/latest/contributing/vulnerability_management/ - FastAPI file uploads:
https://fastapi.tiangolo.com/reference/uploadfile/ - Starlette uploaded files:
https://www.starlette.io/requests/ - Adjacent published audio advisory:
https://github.com/vllm-project/vllm/security/advisories/GHSA-6pr9-rp53-2pmc - Request-parameter resource DoS precedent:
https://github.com/vllm-project/vllm/security/advisories/GHSA-3mwp-wvh9-7528
Appendix: Affected Version
Validated against current head:
- commit:
1033ffac2eccf986fdd880f4dee64ca3b22c63c9 - described version:
v0.22.1rc0-491-g1033ffac2e
Known affected range: current head. It has not been determined the introducing commit or release range.
Appendix: Proof Of Vulnerability
The attached proof is a non-destructive static probe. It does not upload a large file or contact a running vLLM server:
python3 attached-evidence/poc/audio_upload_size_precheck_probe.py
Observed result:
{
"pov": "this report",
"validated": true,
"default_limit_mb": 25,
"documented_api_limit": true,
"routes": {
"transcription_route": {
"unbounded_upload_read": true,
"early_size_guard_before_read": false,
"chunked_bounded_read": false
},
"translation_route": {
"unbounded_upload_read": true,
"early_size_guard_before_read": false,
"chunked_bounded_read": false
}
},
"late_size_check": {
"present": true
}
}
Expected behavior: vLLM rejects over-limit audio files before materializing the entire upload into memory in vLLM endpoint code.
Actual behavior: the route materializes the upload into memory first, and only then does vLLM reject the request as exceeding VLLM_MAX_AUDIO_CLIP_FILESIZE_MB.
Impact
Attack requirements:
- the deployment exposes
/v1/audio/transcriptionsor/v1/audio/translations; - a speech-to-text capable model/task is configured; and
- the caller can submit requests to the endpoint, including any API key the deployment requires.
An API caller who meets those requirements can send an oversized audio file. vLLM reads the full uploaded file into memory before applying the configured compressed audio file-size limit. This can create memory pressure or, depending on process/container limits and concurrency, terminate the process before the request is rejected.
Suggested severity: Moderate, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (6.5), CWE-770/CWE-400.
The impact is availability-only. This is not a claim of code execution, data access, cross-tenant data exposure, parser-level multipart memory exhaustion, or persistence after process restart. Deployment body-size limits at a reverse proxy or ASGI layer can mitigate the issue before vLLM sees the request, but vLLM's own documented file-size limit does not currently provide that memory boundary.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2026-55646 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.24.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Enforce the compressed audio upload limit before the unbounded read:
- Check reliable upload size metadata before reading when available.
- Read at most
max_bytes + 1bytes in chunks as a defense-in-depth guard against missing or unreliable metadata. - Share the helper between transcription and translation routes.
- Add regression tests that prove an over-limit
UploadFileis rejected without calling an unboundedread().
The important property is that over-limit compressed uploads are rejected before vLLM allocates the full uploaded file as bytes.
Frequently Asked Questions
- What is CVE-2026-55646? CVE-2026-55646 is a medium-severity uncontrolled resource consumption vulnerability in vllm (pip), affecting versions >= 0.22.0, < 0.24.0. It is fixed in 0.24.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2026-55646? CVE-2026-55646 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of vllm are affected by CVE-2026-55646? vllm (pip) versions >= 0.22.0, < 0.24.0 is affected.
- Is there a fix for CVE-2026-55646? Yes. CVE-2026-55646 is fixed in 0.24.0. Upgrade to this version or later.
- Is CVE-2026-55646 exploitable, and should I be worried? Whether CVE-2026-55646 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-55646 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-55646? Upgrade
vllmto 0.24.0 or later.