CVE-2026-55646

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.5
EG Score
6.5(medium)
EPSS
20.8%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, github_commit.
github Patch Available🟡 PoC Available

Speech-to-text upload size limit is enforced after full UploadFile read · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-v82g-2437-67m2
github_pr

(security) Enforce audio upload size limit before full file materialization

Fix merged in vllm-project/vllm PR #45510 on 2026-06-15 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/45510
github_commit

commit b997071ec493 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit b997071ec493 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/b997071ec493765abbed990c65843ed05e4708a8

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 05:46 UTCEG score recompute
  4. 2026-07-12 07:47 UTCEG score recompute
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 09:47 UTCEG score recompute
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 11:48 UTCEG score recompute
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 13:47 UTCEG score recompute
  13. 2026-07-08 15:47 UTCEG score recompute
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 17:48 UTCEG score recompute
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 19:47 UTCEG score recompute
  20. 2026-07-06 19:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55646?
CVE-2026-55646 is a medium vulnerability published on July 6, 2026. 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 VLLMMAXAUDIOCLIPFILESIZE_MB…
When was CVE-2026-55646 disclosed?
CVE-2026-55646 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55646 actively exploited?
CVE-2026-55646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55646?
CVE-2026-55646 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-55646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55646, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55646

Explore →

Is Your Infrastructure Affected by CVE-2026-55646?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs