# CVE-2026-18618: Ml-metdata: bundled grpc 1.46.3 (2022) with published http/2 dos cves — directly reachable on listener

> An in-cluster attacker can crash the ML Metadata pod via crafted HTTP/2 requests, disrupting pipeline runs in OpenShift AI.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-cr6h-6g58-pq2g

## What is CVE-2026-18618?

CVE-2026-18618 is a high-severity denial of service vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-18618?


## How do I fix CVE-2026-18618?

No fix has been published for CVE-2026-18618 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18618 being exploited?

There is no known exploitation of CVE-2026-18618 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18618 and fix it if it is affected.

What it is: CVE-2026-18618 is a high-severity denial of service vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18618 in the wild and no public exploit code.

Affected product: Red Hat OpenShift AI 2.25. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18618/ (Markdown: https://insights.sbomify.com/CVE-2026-18618/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18618
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18618
- OSV: https://osv.dev/vulnerability/CVE-2026-18618

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18618/
Summaries are generated and may contain mistakes; the official description above is the record.