Introduction
A NodeJS endpoint in the odh-dashboard component of Red Hat OpenShift AI leaks Kubernetes Service Account tokens to unauthorized actors. The leak gives those actors a direct path to cluster resources. CVE-2026-5483 has a CVSS score of 8.5, and it is a serious risk for any organization running OpenShift AI, because the dashboard's service accounts often carry the elevated privileges needed to orchestrate machine learning workloads.
Red Hat OpenShift AI is a hybrid AI and MLOps platform built on top of Red Hat OpenShift. It provides tooling for training, serving, and monitoring models across the full lifecycle of AI and ML experiments. The odh-dashboard is the central user interface and management plane for this work, which makes it a high-value target in any deployment.
Technical Information
Root Cause
The vulnerability falls under CWE-201: Insertion of Sensitive Information Into Sent Data. The odh-dashboard component exposes a NodeJS endpoint that returns Kubernetes Service Account tokens in its response when queried. Services use these tokens as credentials to authenticate against the Kubernetes API server. The endpoint does not strip or redact them before it sends the response to the client.
Why This Matters in Context
Unlike a lightweight frontend, the odh-dashboard manages custom resources such as OdhApplication and coordinates AI workloads across the cluster. To do that, the service accounts bound to the dashboard typically hold significant Kubernetes RBAC permissions. A token from one of these accounts could let an attacker list, create, modify, or delete resources well beyond the dashboard's own scope.
Attack Flow
Based on the available information, exploitation follows these steps:
- An attacker finds a reachable instance of the
odh-dashboardNodeJS service. Many deployments expose the dashboard through an OpenShift Route or Ingress so users can reach it. - The attacker sends a request to the vulnerable endpoint. Red Hat has not publicly disclosed the specific endpoint path.
- The endpoint responds with data that includes one or more Kubernetes Service Account tokens.
- The attacker extracts a token and uses it to authenticate directly against the Kubernetes API server (for example, with
kubectlor raw API calls). - Depending on the RBAC permissions bound to the compromised service account, the attacker can enumerate secrets, deploy workloads, access persistent volumes, or pivot to other namespaces in the cluster.
Missing Details
The exact vulnerable endpoint path, precise reproduction steps, and a complete list of affected product versions have not been made public. Administrators should consult the official Red Hat security errata for these specifics.
Affected Systems and Versions
The vulnerability affects the odh-dashboard component of Red Hat OpenShift AI (RHOAI). The materials currently available from Red Hat do not give the exact version range. Organizations should check advisory RHSA-2026:7397 and Bugzilla entry 2454764 for the definitive list of affected versions and fixed packages.
Vendor Security History
Red Hat runs a dedicated Product Security Center. It publishes security advisories, maintains a CVE database that tracks vulnerabilities across Red Hat products, and ships continuous security updates, with backporting policies for enterprise lifecycle support. Because of this program, patches and severity classifications for issues like CVE-2026-5483 typically arrive on a predictable schedule. The publication of RHSA-2026:7397 is consistent with Red Hat's established response process.
References
- NVD Entry for CVE-2026-5483
- Red Hat Security Advisory RHSA-2026:7397
- Red Hat CVE Page for CVE-2026-5483
- Bugzilla: CVE-2026-5483 odh-dashboard Kubernetes Service Account Exposure
- Red Hat OpenShift AI Product Page
- Red Hat Customer Portal: Product Security Center
- Managing Applications in the OpenShift AI Dashboard
