Vulnerability in vllm (CVE-2026-55646)
Summary
Vulnerability in vllm (CVE-2026-55646). Risk of unauthorized operations or information disclosure. Exploitable via VLLM_MAX_AUDIO_CLIP_FILESIZE_MB. Mitigation: upgrade to 0.24.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55646 has been found in vllm.
Attackers can target a specific entry point like VLLM_MAX_AUDIO_CLIP_FILESIZE_MB over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade vllm to 0.24.0 or later.
If unsure, ask your IT team or search "vllm CVE-2026-55646" on the vendor's site.
CVE-2026-55646 (vllm) — CWE-400 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: VLLM_MAX_AUDIO_CLIP_FILESIZE_MB / bytes / request.file.size / VLLM_MAX_N_SEQUENCES
Patched: 0.24.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in vllm. Attackers reach the vulnerable code path via VLLM_MAX_AUDIO_CLIP_FILESIZE_MB.
Check the vendor advisory for the affected versions of vllm. Attack surface: VLLM_MAX_AUDIO_CLIP_FILESIZE_MB / bytes / request.file.size / VLLM_MAX_N_SEQUENCES.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.24.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vllm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vllm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vllmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade vllm to 0.24.0ステージング環境で 0.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com