CVE-2026-18949 json
Odh-dashboard: odh-dashboard: clusterrole grants cluster-wide crud on secrets and rbac management resources
published 2026-08-10 2 mo ago modified 2026-10-22 18 d ago also EUVD-2026-55819
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Red Hat Red Hat OpenShift AI 2.25 1785940823, 1791853432
- Red Hat Red Hat OpenShift AI 3.3 1786109683
- Red Hat Red Hat OpenShift AI 3.4 1786109665, 1791860708, 1791860918, 1791860994, 1791861032, 1791861214, 1791861383, 1791861479
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-18949 updated cvss 8.8
odh-dashboard: odh-dashboard: ClusterRole grants cluster-wide CRUD on secrets and RBAC management resources
-
Red Hat OpenShift AI 2.25 rhoai/odh-dashboard-rhel9 1785940823, rhoai/odh-mod-arch-model-registry-rhel9 1791853432fixed: vendor fix RHSA-2026:53261
-
Red Hat OpenShift AI 3.3 rhoai/odh-dashboard-rhel9 1786109683fixed: vendor fix RHSA-2026:53263
-
Red Hat OpenShift AI 3.4 rhoai/odh-dashboard-rhel9 1786109665, rhoai/odh-mod-arch-maas-rhel9 1791860708, rhoai/odh-mod-arch-automl-rhel9 1791861032, rhoai/odh-mod-arch-gen-ai-rhel9 1791861479, rhoai/odh-mod-arch-mlflow-rhel9 1791861383, rhoai/odh-mod-arch-autorag-rhel9 1791860994, +2 morefixed: vendor fix RHSA-2026:53262
-
Red Hat OpenShift AI 2.25 rhoai/odh-rhel9-operator 1786112809, rhoai/odh-rhel9-operator 1792570619, rhoai/odh-vllm-cpu-rhel9 1792018436, rhoai/odh-dashboard-rhel9 1791853525, rhoai/odh-modelmesh-rhel9 1790881700, rhoai/odh-operator-bundle 1786113363, +90 more Red Hat OpenShift AI 3.3 rhoai/odh-trainer-rhel9 1785187865, rhoai/odh-rhel9-operator 1786129846, rhoai/odh-operator-bundle 1786130475, rhoai/odh-ta-lmes-job-rhel9 1785187607, rhoai/odh-mod-arch-maas-rhel9 1786109736, rhoai/odh-feast-operator-rhel9 1786110087, +21 more Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1791509689, rhoai/rhai-cli-rhel9 1791509689, rhoai/odh-automl-rhel9 1791535789, rhoai/odh-mlflow-rhel9 1791865967, rhoai/odh-autorag-rhel9 1791557539, rhoai/odh-trainer-rhel9 1784039162, +129 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 mo ago
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Red Hat Red Hat OpenShift AI 2.25
- Red Hat Red Hat OpenShift AI 3.3
- Red Hat Red Hat OpenShift AI 3.4
Classification
- Weakness
-
- CWE-250 Execution with Unnecessary Privileges
References
-
access.redhat.com
/errata/RHSA-2026:53261
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:53262
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:53263
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:84734
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:87410
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-18949
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2511168
issue-tracking
Sources
- CVE List CVE-2026-18949
- NVD CVE-2026-18949
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.