# CVE-2026-18951: Missing authorization in Red Hat OpenShift AI 3.3

> Users with edit permissions can manage TrainJobs, enabling privilege escalation and code execution when combined with pod configuration flaws.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-h7xh-qc2m-rc58

## What is CVE-2026-18951?

CVE-2026-18951 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI 3.3, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Red Hat OpenShift AI (RHOAI) overlay for the training operator. The RHOAI overlay incorrectly aggregates `trainjobs` management permissions into the native Kubernetes `edit ClusterRole`. This allows any user with `edit ClusterRole` permissions in a namespace to create, modify, and delete `TrainJobs`. When combined with a separate vulnerability (TRN-01) that permits arbitrary pod configurations, a remote attacker with namespace editor privileges could exploit this to escalate privileges, potentially leading to arbitrary code execution.

Weakness: CWE-284 (Improper Access Control), CWE-267 (Privilege Defined With Unsafe Actions)

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


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

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

## Is CVE-2026-18951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18951 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI 3.3, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18951 in the wild and no public exploit code.

Affected product: Red Hat OpenShift AI 3.3. 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-18951/ (Markdown: https://insights.sbomify.com/CVE-2026-18951/index.md)
```

## Sources

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

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