# CVE-2026-15467: Security feature bypass in Red Hat OpenShift AI 2.25

> Authenticated users can bypass security policies to execute untrusted remote code in OpenShift AI clusters via sidecar container configuration.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 21 Sep 2026
- **Also known as:** GHSA-qw34-v3jw-3crv

## What is CVE-2026-15467?

CVE-2026-15467 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, 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 trustyai-service-operator's LMEvalJob controller. An authenticated user within the cluster can exploit this vulnerability by configuring a sidecar container to bypass existing security policies. This allows the user to enable and execute untrusted remote code, leading to arbitrary code execution within the cluster.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-15467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15467 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, 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-15467 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-15467/ (Markdown: https://insights.sbomify.com/CVE-2026-15467/index.md)
```

## Sources

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

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