CVE-2026-73560

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 75% 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
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 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.26.0, the MiMoV2OmniMultiModalProcessor in vllm/transformers_utils/processors/mimo_v2_omni.py passes attacker-controlled image and audio strings through _fetch_image, requests.get, and Image.open instead of MediaConnector, bypassing allowed_media_domains and allowed_local_media_path protections and allowing server-side requests and reads of arbitrary files accessible to the vLLM process. This issue is fixed in version 0.26.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v0.26.0

Patch available: vllm-project/vllm v0.26.0

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

commit 54503ecec0f3 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/54503ecec0f3ac31e5ecfc5f28652e4cc42307b5
github_pr

fix(processor): route MiMo-V2-Omni media fetch through MediaConnector

Fix merged in vllm-project/vllm PR #43117 on 2026-07-11 — awaiting tagged release

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

SSRF + arbitrary local file read in MiMoV2OmniMultiModalProcessor `_fetch_image` and audio loader bypass MediaConnector protections · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-4hhp-h66f-j5j7

Vendor Advisories for CVE-2026-73560(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 (92 versions)0.26.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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 20:09 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 22:03 UTCEG score recompute
  4. 2026-09-16 23:05 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 21:27 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 22:24 UTCEG score recompute
  10. 2026-09-12 23:27 UTCEG score recompute
  11. 2026-09-12 15:02 UTCEPSS rescore
  12. 2026-09-12 00:30 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 01:32 UTCEG score recompute
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-09 03:38 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 21:09 UTCEG score recompute
  19. 2026-09-06 22:11 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 23:10 UTCEG score recompute
  22. 2026-09-05 00:13 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-03 00:44 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 35 more
  1. 2026-09-02 01:47 UTCEG score recompute
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-31 03:22 UTCEG score recompute
  6. 2026-08-30 19:18 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 04:24 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 05:24 UTCEG score recompute
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 06:21 UTCEG score recompute
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-27 07:23 UTCEG score recompute
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:26 UTCEG score recompute
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 09:28 UTCEG score recompute
  19. 2026-08-24 10:31 UTCEG score recompute
  20. 2026-08-23 11:32 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 12:35 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 13:38 UTCEG score recompute
  25. 2026-08-20 22:56 UTCEPSS rescore
  26. 2026-08-20 14:40 UTCEG score recompute
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 15:43 UTCEG score recompute
  29. 2026-08-18 16:46 UTCEG score recompute
  30. 2026-08-18 16:14 UTCEG score recompute
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-18 13:49 UTCEPSS rescore
  33. 2026-08-17 21:32 UTCEG score recompute
  34. 2026-08-17 20:30 UTCEG score recompute
  35. 2026-08-17 20:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73560?
CVE-2026-73560 is a medium vulnerability published on August 17, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.26.0, the MiMoV2OmniMultiModalProcessor in vllm/transformersutils/processors/mimov2omni.py passes attacker-controlled image and audio strings through fetchimage, requests.get, and Image.open instead of MediaConnector,…
When was CVE-2026-73560 disclosed?
CVE-2026-73560 was first published in the National Vulnerability Database on August 17, 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-73560 actively exploited?
CVE-2026-73560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-73560?
CVE-2026-73560 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-73560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73560, 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-73560

Explore →

Is Your Infrastructure Affected by CVE-2026-73560?

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

Start Free Scan →Browse All CVEs