CVE-2026-57173

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.7%, top 50% 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 week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 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. Prior to 0.24.0, the input_audio handling path for /v1/chat/completions calls AudioMediaIO.load_bytes or AudioMediaIO.load_file without passing VLLM_MAX_AUDIO_DECODE_DURATION_S to the shared audio decoder. An unauthenticated client can therefore submit a small compressed audio input that expands into a very large float32 PCM allocation, bypassing the duration guard already used by /v1/audio/transcriptions and causing an out-of-memory worker crash. Inline data URLs reach this path without being bounded by VLLM_AUDIO_FETCH_TIMEOUT. The issue affects deployments serving an audio-capable model, and authentication changes only the deployment-specific reachability. This issue is fixed in version 0.24.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v0.24.0

Patch available: vllm-project/vllm v0.24.0

https://github.com/vllm-project/vllm/releases/tag/v0.24.0
github_commit

commit 3d20275bb4d4 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/3d20275bb4d434f53055c3c0b645fd8bb072965e
github_pr

fix(security): enforce audio decode duration limit in chat completions path

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

https://github.com/vllm-project/vllm/pull/45908
github Patch Available

Unauthenticated audio decompression-bomb DoS in /v1/chat/completions: VLLM_MAX_AUDIO_DECODE_DURATION_S guard not wired into the chat audio path (sibling of CVE-2026-5497) · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-hcwq-8wjf-3gcr

Vendor Advisories for CVE-2026-57173(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vllm0.0.1 ... 0.9.2 (89 versions)0.24.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:32 UTCEG score recompute
  3. 2026-09-18 18:15 UTCEG score recompute
  4. 2026-09-18 14:15 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescore
  6. 2026-09-16 17:29 UTCEG score recompute
  7. 2026-09-16 16:46 UTCEG score recompute
  8. 2026-09-16 16:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57173?
CVE-2026-57173 is a medium vulnerability published on September 16, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.24.0, the inputaudio handling path for /v1/chat/completions calls AudioMediaIO.loadbytes or AudioMediaIO.loadfile without passing VLLMMAXAUDIODECODEDURATIONS to the shared audio decoder. An unauthenticated client can…
When was CVE-2026-57173 disclosed?
CVE-2026-57173 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57173 actively exploited?
CVE-2026-57173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.0% of all scored CVEs.
What is the CVSS score of CVE-2026-57173?
CVE-2026-57173 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-57173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57173, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57173

Explore →

Is Your Infrastructure Affected by CVE-2026-57173?

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