CVE-2026-18618 json
Ml-metdata: bundled grpc 1.46.3 (2022) with published http/2 dos cves — directly reachable on listener
published 2026-08-10 2 mo ago modified 2026-10-19 21 d ago also EUVD-2026-55825
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Red Hat Red Hat OpenShift AI 2.25 1785260280
- Red Hat Red Hat OpenShift AI 3.3 1785262015
- Red Hat Red Hat OpenShift AI 3.4 1785269945, 1791865241
- Red Hat Red Hat OpenShift AI 3.5 1786552250, 1786552271
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-18618 updated cvss 7.5
ml-metdata: Bundled gRPC 1.46.3 (2022) with published HTTP/2 DoS CVEs — directly reachable on listener
-
Red Hat OpenShift AI 2.25 rhoai/odh-mlmd-grpc-server-rhel9 1785260280fixed: vendor fix RHSA-2026:53261
-
Red Hat OpenShift AI 3.3 rhoai/odh-mlmd-grpc-server-rhel9 1785262015fixed: vendor fix RHSA-2026:53263
-
Red Hat OpenShift AI 3.4 rhoai/odh-mlmd-grpc-server-rhel9 1785269945, rhoai/odh-mlmd-grpc-server-rhel9 1791865241fixed: vendor fix RHSA-2026:53262
-
Red Hat OpenShift AI 3.5 rhoai/odh-latency-predictor-training-rhel9 1786552250, rhoai/odh-latency-predictor-prediction-rhel9 1786552271fixed: vendor fix RHSA-2026:60367
-
Red Hat OpenShift AI 2.25 rhoai/odh-rhel9-operator 1786112809, rhoai/odh-dashboard-rhel9 1785940823, rhoai/odh-operator-bundle 1786113363, rhoai/odh-caikit-nlp-rhel9 1785186995, rhoai/odh-ta-lmes-job-rhel9 1785187011, rhoai/odh-feast-operator-rhel9 1786110116, +19 more Red Hat OpenShift AI 3.3 rhoai/odh-trainer-rhel9 1785187865, rhoai/odh-rhel9-operator 1786129846, rhoai/odh-dashboard-rhel9 1786109683, rhoai/odh-operator-bundle 1786130475, rhoai/odh-ta-lmes-job-rhel9 1785187607, rhoai/odh-mod-arch-maas-rhel9 1786109736, +21 more Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1791509689, rhoai/rhai-cli-rhel9 1791509689, rhoai/odh-automl-rhel9 1791535789, rhoai/odh-mlflow-rhel9 1791865967, rhoai/odh-autorag-rhel9 1791557539, rhoai/odh-trainer-rhel9 1784039162, +135 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Red Hat Red Hat OpenShift AI 2.25
- Red Hat Red Hat OpenShift AI 3.3
- Red Hat Red Hat OpenShift AI 3.4
- Red Hat Red Hat OpenShift AI 3.5
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
access.redhat.com
/errata/RHSA-2026:53261
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:53262
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:53263
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:60367
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:84734
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-18618
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2510313
issue-tracking
Sources
- CVE List CVE-2026-18618
- NVD CVE-2026-18618
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.