CVE-2026-18618

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in ml-metadata. The statically-linked gRPC stack in ml-metadata is outdated, making it vulnerable to known HTTP/2 denial of service (DoS) issues. An in-cluster attacker, with network access to the MLMD pod, could exploit these vulnerabilities by sending specially crafted HTTP/2 requests. This could lead to a denial of service by crashing the MLMD pod, disrupting all pipeline runs in the affected namespace.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

September 21, 2026

Advisory Details (2)

Auto-updated Aug 10, 2026
Patch available. Sources: redhat.
redhat

2510313 – (CVE-2026-18618) CVE-2026-18618 ml-metdata: Bundled gRPC 1.46.3 (2022) with published HTTP/2 DoS CVEs — directly reachable on listener

https://bugzilla.redhat.com/show_bug.cgi?id=2510313
redhat Patch Available

CVE-2026-18618 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-18618

Vendor Advisories for CVE-2026-18618(5)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-latency-predictor-training-rhel9:17865522502026-08-26redhat
redhatrhoai/odh-mlmd-grpc-server-rhel9:17852602802026-08-11redhat
redhatrhoai/odh-mlmd-grpc-server-rhel9:17852620152026-08-11redhat
redhatrhoai/odh-mlmd-grpc-server-rhel9:17852699452026-08-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 140× 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.

Showing the most recent 100 of 293 total refreshes for this CVE.

  1. 2026-10-05 02:35 UTCEG score recompute
  2. 2026-10-05 02:35 UTCVendor advisory
  3. 2026-10-05 02:35 UTCGHSA enrichment
  4. 2026-10-04 23:21 UTCEPSS rescore
  5. 2026-10-04 12:24 UTCVendor advisory
  6. 2026-10-04 12:24 UTCGHSA enrichment
  7. 2026-10-03 22:45 UTCEG score recompute
  8. 2026-10-03 22:45 UTCVendor advisory
  9. 2026-10-03 22:45 UTCGHSA enrichment
  10. 2026-10-03 14:25 UTCEPSS rescore
  11. 2026-10-02 22:34 UTCEG score recompute
  12. 2026-10-02 22:34 UTCVendor advisory
  13. 2026-10-02 22:34 UTCGHSA enrichment
  14. 2026-10-02 09:16 UTCEG score recompute
  15. 2026-10-02 09:16 UTCVendor advisory
  16. 2026-10-02 09:16 UTCGHSA enrichment
  17. 2026-10-01 19:49 UTCEPSS rescore
  18. 2026-10-01 10:53 UTCVendor advisory
  19. 2026-10-01 10:53 UTCGHSA enrichment
  20. 2026-09-30 22:24 UTCEG score recompute
  21. 2026-09-30 22:24 UTCVendor advisory
  22. 2026-09-30 22:24 UTCGHSA enrichment
  23. 2026-09-30 15:02 UTCEPSS rescore
  24. 2026-09-29 15:20 UTCEPSS rescore
  25. 2026-09-29 05:20 UTCEG score recompute
Show 75 more
  1. 2026-09-29 05:20 UTCVendor advisory
  2. 2026-09-29 05:20 UTCGHSA enrichment
  3. 2026-09-28 13:51 UTCEPSS rescore
  4. 2026-09-28 02:22 UTCEG score recompute
  5. 2026-09-28 02:22 UTCVendor advisory
  6. 2026-09-28 02:22 UTCGHSA enrichment
  7. 2026-09-27 13:47 UTCEPSS rescore
  8. 2026-09-27 11:08 UTCEG score recompute
  9. 2026-09-27 11:08 UTCVendor advisory
  10. 2026-09-27 11:08 UTCGHSA enrichment
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-25 03:59 UTCEG score recompute
  13. 2026-09-25 03:59 UTCVendor advisory
  14. 2026-09-25 03:59 UTCGHSA enrichment
  15. 2026-09-24 02:05 UTCEG score recompute
  16. 2026-09-24 02:05 UTCVendor advisory
  17. 2026-09-24 02:04 UTCGHSA enrichment
  18. 2026-09-23 13:46 UTCVendor advisory
  19. 2026-09-23 13:46 UTCGHSA enrichment
  20. 2026-09-23 01:27 UTCEG score recompute
  21. 2026-09-23 01:27 UTCVendor advisory
  22. 2026-09-23 01:27 UTCGHSA enrichment
  23. 2026-09-22 13:08 UTCVendor advisory
  24. 2026-09-22 13:08 UTCGHSA enrichment
  25. 2026-09-22 00:49 UTCEG score recompute
  26. 2026-09-22 00:49 UTCVendor advisory
  27. 2026-09-22 00:49 UTCGHSA enrichment
  28. 2026-09-21 12:30 UTCEG score recompute
  29. 2026-09-21 12:30 UTCVendor advisory
  30. 2026-09-21 12:30 UTCGHSA enrichment
  31. 2026-09-21 11:35 UTCEG score recompute
  32. 2026-09-21 11:35 UTCVendor advisory
  33. 2026-09-21 11:35 UTCGHSA enrichment
  34. 2026-09-21 11:05 UTCEG score recompute
  35. 2026-09-21 11:05 UTCVendor advisory
  36. 2026-09-21 11:05 UTCGHSA enrichment
  37. 2026-09-20 19:56 UTCVendor advisory
  38. 2026-09-20 19:56 UTCGHSA enrichment
  39. 2026-09-20 05:36 UTCVendor advisory
  40. 2026-09-20 05:36 UTCGHSA enrichment
  41. 2026-09-19 17:17 UTCEG score recompute
  42. 2026-09-19 17:17 UTCVendor advisory
  43. 2026-09-19 17:17 UTCGHSA enrichment
  44. 2026-09-19 03:05 UTCEG score recompute
  45. 2026-09-19 03:05 UTCVendor advisory
  46. 2026-09-19 03:04 UTCGHSA enrichment
  47. 2026-09-18 19:27 UTCEPSS rescore
  48. 2026-09-18 14:44 UTCVendor advisory
  49. 2026-09-18 14:44 UTCGHSA enrichment
  50. 2026-09-18 02:25 UTCEG score recompute
  51. 2026-09-18 02:25 UTCVendor advisory
  52. 2026-09-18 02:25 UTCGHSA enrichment
  53. 2026-09-17 14:06 UTCVendor advisory
  54. 2026-09-17 14:06 UTCGHSA enrichment
  55. 2026-09-17 00:40 UTCEG score recompute
  56. 2026-09-17 00:40 UTCVendor advisory
  57. 2026-09-17 00:40 UTCGHSA enrichment
  58. 2026-09-16 14:07 UTCEPSS rescore
  59. 2026-09-16 05:14 UTCEPSS rescore
  60. 2026-09-16 02:23 UTCVendor advisory
  61. 2026-09-16 02:23 UTCGHSA enrichment
  62. 2026-09-15 13:41 UTCEG score recompute
  63. 2026-09-15 13:41 UTCVendor advisory
  64. 2026-09-15 13:41 UTCGHSA enrichment
  65. 2026-09-14 22:51 UTCVendor advisory
  66. 2026-09-14 22:51 UTCGHSA enrichment
  67. 2026-09-14 09:10 UTCVendor advisory
  68. 2026-09-14 09:10 UTCGHSA enrichment
  69. 2026-09-13 20:52 UTCEG score recompute
  70. 2026-09-13 20:52 UTCVendor advisory
  71. 2026-09-13 20:52 UTCGHSA enrichment
  72. 2026-09-13 16:46 UTCEPSS rescore
  73. 2026-09-13 08:33 UTCVendor advisory
  74. 2026-09-13 08:33 UTCGHSA enrichment
  75. 2026-09-12 20:15 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-18618?
CVE-2026-18618 is a high vulnerability published on August 10, 2026. A flaw was found in ml-metadata. The statically-linked gRPC stack in ml-metadata is outdated, making it vulnerable to known HTTP/2 denial of service (DoS) issues. An in-cluster attacker, with network access to the MLMD pod, could exploit these vulnerabilities by sending specially crafted HTTP/2…
When was CVE-2026-18618 disclosed?
CVE-2026-18618 was first published on August 10, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18618 actively exploited?
CVE-2026-18618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18618?
CVE-2026-18618 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18618?
A fix for CVE-2026-18618 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18618 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-18618?

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

Book a Demo →Browse All CVEs