# CVE-2026-15581: Missing authorization in Red Hat OpenShift AI 2.25

> Attackers can bypass authentication to read, modify, or delete monitoring data and configurations in TrustyAI Service deployments.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-7rjm-5cpg-vwpq

## What is CVE-2026-15581?

CVE-2026-15581 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the TrustyAI Service (TAS) deployment. This vulnerability allows any pod on the cluster network to bypass authentication and directly access the TAS backend API. An attacker can exploit this to read, tamper with, or delete monitoring data and configurations, and inject arbitrary data into the service, potentially disrupting tenant operations.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-15581 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15581 is a high-severity missing authorization vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15581 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-15581/ (Markdown: https://insights.sbomify.com/CVE-2026-15581/index.md)
```

## Sources

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

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