What is the CVSS score of CVE-2026-5483?

CVE-2026-5483 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of OpenShift AI are affected by CVE-2026-5483?

Red Hat OpenShift AI's dashboard component contains a critical vulnerability allowing authenticated users to extract Kubernetes service account tokens and escalate to full cluster access.. A patch is available.

How to fix or mitigate CVE-2026-5483?

24 hours: Identify and audit all Red Hat OpenShift AI deployments and current dashboard users. 7 days: Apply Red Hat's released patch for CVE-2026-5483 per vendor errata across all RHOAI instances. 30 days: Verify successful patch deployment and review Kubernetes audit logs for suspicious service account token access between initial discovery and patch application.

OpenShift AI CVE-2026-5483

EUVD-2026-21547 CRITICAL

Insertion of Sensitive Information Into Sent Data (CWE-201)

2026-04-10 redhat

GHSA-w59f-v72r-w493

Authentication Bypass Kubernetes Red Hat Red Hat Openshift Ai Rhoai Red Hat Openshift Ai 2 16 Red Hat

9.9

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.9 CRITICAL

Network-reachable endpoint exploitable by a low-priv authenticated dashboard user (PR:L, AC:L); the leaked SA token authenticates to the Kubernetes API, crossing a scope boundary (S:C) with full C/I/A impact on cluster resources.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

Red Hat

8.5 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Jun 30, 2026 - 03:51 vuln.today

v5 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 03:48 vuln.today

v4 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 03:47 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 03:47 vuln.today

v2 (cvss_changed)

Severity Changed

Jun 30, 2026 - 03:24 NVD

HIGH CRITICAL

CVSS changed

Jun 30, 2026 - 03:24 NVD

8.5 (HIGH) 9.9 (CRITICAL)

Re-analysis Queued

Apr 21, 2026 - 19:52 vuln.today

cvss_changed

EUVD ID Assigned

Apr 10, 2026 - 18:00 euvd

EUVD-2026-21547

Analysis Generated

Apr 10, 2026 - 18:00 vuln.today

CVE Published

Apr 10, 2026 - 17:33 nvd

HIGH 8.5

DescriptionNVD

A flaw was found in odh-dashboard in Red Hat Openshift AI. This vulnerability in the odh-dashboard component of Red Hat OpenShift AI (RHOAI) allows for the disclosure of Kubernetes Service Account tokens through a NodeJS endpoint. This could enable an attacker to gain unauthorized access to Kubernetes resources.

AnalysisAI

Kubernetes Service Account token disclosure in the odh-dashboard component of Red Hat OpenShift AI (RHOAI) lets an authenticated low-privileged user retrieve SA tokens via an exposed NodeJS endpoint, then reuse them to reach Kubernetes resources beyond the dashboard's intended scope. Rated CVSS 9.9 with a changed scope, the flaw effectively converts limited dashboard access into broad cluster access. There is no public exploit identified at time of analysis and EPSS is very low (0.06%), but a vendor patch is already available via Red Hat errata.

Technical ContextAI

OpenShift AI (RHOAI) is Red Hat's machine-learning platform that runs on OpenShift/Kubernetes; odh-dashboard is its Node.js-based web frontend (derived from Open Data Hub). In Kubernetes, Service Account tokens are bearer credentials that the API server accepts for authentication and authorization - possession of a token grants whatever RBAC the associated SA holds. The root cause maps to CWE-201 (Insertion of Sensitive Information Into Sent Data): a dashboard backend endpoint returns SA token material to the client rather than keeping it server-side, exposing a credential that should never transit to the user. Because the leaked token authenticates directly to the Kubernetes API, the impact crosses a trust boundary from the application to the cluster control plane, which is reflected in the CVSS scope change (S:C).

RemediationAI

Apply the Red Hat fix by upgrading odh-dashboard / RHOAI to the patched releases shipped in the errata - Red Hat OpenShift AI 2.16 (patched image digest sha256:0a983da3...110341) and 3.3 (sha256:14ee2bbd...3293e); pull the updated operator/dashboard images per RHSA-2026:7397 (and related RHSA-2026:7403/7398/7404) at https://access.redhat.com/errata/RHSA-2026:7397 and the CVE page https://access.redhat.com/security/cve/CVE-2026-5483. Until patching is complete, reduce exposure by restricting network access to the odh-dashboard route (limit it to trusted networks/VPN or an authenticating reverse proxy) and tightening who holds dashboard access, since that limits which users can reach the leaking endpoint; as a containment measure, scope down RBAC on the affected Service Account(s) and rotate any SA tokens that may have been exposed so leaked credentials lose validity. Trade-offs: restricting the route or rotating tokens can disrupt legitimate data-science users and running workloads, so coordinate token rotation with workload owners. Track remediation against the Bugzilla record https://bugzilla.redhat.com/show_bug.cgi?id=2454764.