CVE-2026-73560

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 17, 2026

Last Modified

September 28, 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 pull request

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 advisoryMentions a patch (unverified)

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(6)

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 rangeFix by version rangeDependents
vllm0.0.1 ... 0.9.2 (92 versions)
  • every version up to 0.26.0: fixed in 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 / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 97 are merged into the row they repeat.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-12 15:40 UTCEG score recompute
  4. 2026-10-11 19:26 UTCEG score recompute
  5. 2026-10-11 16:42 UTCEG score recompute
  6. 2026-10-11 14:01 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-06 17:10 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-05 17:25 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-03 17:46 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-02 08:04 UTCEG score recompute
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-01 08:57 UTCEG score recompute
  22. 2026-09-30 09:58 UTCEG score recompute
  23. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-09-28 18:56 UTCEG score recompute
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 69 more
  1. 2026-09-28 07:04 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-09-27 08:05 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-09-25 02:00 UTCEG score recompute
  6. 2026-09-23 20:27 UTCEG score recompute
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-09-22 20:40 UTCEG score recompute
  9. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-09-21 18:38 UTCEG score recompute
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-09-19 19:30 UTCEG score recompute
  13. 2026-09-18 20:09 UTCEG score recompute
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-09-17 22:03 UTCEG score recompute
  16. 2026-09-16 23:05 UTCEG score recompute
  17. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-09-15 21:27 UTCEG score recompute
  20. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-13 22:24 UTCEG score recompute
  22. 2026-09-12 23:27 UTCEG score recompute
  23. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-09-12 00:30 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-09-11 01:32 UTCEG score recompute
  27. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-09-09 03:38 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-09-07 21:09 UTCEG score recompute
  31. 2026-09-06 22:11 UTCEG score recompute
  32. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-05 23:10 UTCEG score recompute
  34. 2026-09-05 00:13 UTCEG score recompute
  35. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-09-03 00:44 UTCEG score recompute
  37. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-09-02 01:47 UTCEG score recompute
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  41. 2026-08-31 03:22 UTCEG score recompute
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-08-30 04:24 UTCEG score recompute
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-08-29 05:24 UTCEG score recompute
  46. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  47. 2026-08-28 06:21 UTCEG score recompute
  48. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-08-27 07:23 UTCEG score recompute
  50. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-08-26 08:26 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-08-25 09:28 UTCEG score recompute
  54. 2026-08-24 10:31 UTCEG score recompute
  55. 2026-08-23 11:32 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-08-22 12:35 UTCEG score recompute
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-08-21 13:38 UTCEG score recompute
  60. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-08-20 14:40 UTCEG score recompute
  62. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-08-19 15:43 UTCEG score recompute
  64. 2026-08-18 16:46 UTCEG score recompute
  65. 2026-08-18 16:14 UTCEG score recompute
  66. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-08-17 21:32 UTCEG score recompute
  68. 2026-08-17 20:30 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  69. 2026-08-17 20:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73560?
CVE-2026-73560 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-73560 published?
The CVE record for CVE-2026-73560 was published on August 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-73560 actively exploited?
CVE-2026-73560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73560?
CVE-2026-73560 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73560?
A fix for CVE-2026-73560 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73560 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs