# CVE-2026-18949: Odh-dashboard: odh-dashboard: clusterrole grants cluster-wide crud on secrets and rbac management resources

> Attackers with compromised dashboard service account tokens can escalate to cluster-admin, accessing sensitive data and disrupting isolation.

- **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:** 22 Oct 2026
- **Also known as:** GHSA-vccp-8mm3-h2f6

## What is CVE-2026-18949?

CVE-2026-18949 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 odh-dashboard. This vulnerability allows an attacker, who has compromised the dashboard's Service Account (SA) token, to exploit overly broad permissions granted to the SA. This enables the attacker to escalate their privileges to cluster-administrator level, gain access to sensitive data like credentials and keys across the entire cluster, and disrupt multi-tenant isolation.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2026-18949 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18949 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-18949 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-18949/ (Markdown: https://insights.sbomify.com/CVE-2026-18949/index.md)
```

## Sources

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

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