Security readout for executives and security teams
Plain-English summary
A Red Hat OpenShift AI dashboard flaw can expose Kubernetes service account tokens through a NodeJS endpoint. An attacker with some privileges could use those tokens to access Kubernetes resources they should not reach. Because tokens can carry broad cluster permissions, the business risk is unauthorized access to AI platform workloads, data, or control-plane resources.
Executive priority
Treat as high priority for RHOAI environments because exposed Kubernetes service account tokens can undermine platform boundaries. Prioritize internet-adjacent, shared, or multi-tenant AI clusters first. No active exploitation is evidenced in the provided bundle, but the potential impact is broad cluster resource access.
Technical view
CVE-2026-5483 affects odh-dashboard in RHOAI and is classified as CWE-201. CVSS is 8.5: network attack vector, high complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The source describes token disclosure through a NodeJS endpoint, not a full exploitation chain.
Likely exposure
Likely exposure is RHOAI deployments running affected odh-dashboard packages: rhoai/odh-dashboard-rhel8 in 2.16 and rhoai/odh-dashboard-rhel9 in 2.25, 3.2, or 3.3. The bundle lists several odh-mod-arch packages as unaffected. Other products are not supported by the provided evidence.
Exploitation context
The provided sources do not show KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires low privileges and high attack complexity, with no user interaction. Risk rises where the dashboard endpoint is reachable by untrusted authenticated users or service account tokens grant broad Kubernetes permissions.
Researcher notes
Do not assume unauthenticated exploitation or public exploit availability from the provided data. The evidence supports token disclosure via a NodeJS endpoint in odh-dashboard with PR:L and AC:H. Focus validation on affected package presence, endpoint exposure, token scope, and whether Red Hat advisory updates have been applied.
Mitigation direction
- Review the Red Hat CVE page and relevant RHSA advisories for official remediation.
- Prioritize updating affected odh-dashboard packages in RHOAI 2.16, 2.25, 3.2, and 3.3.
- Restrict access to odh-dashboard endpoints to trusted users and networks where feasible.
- Audit Kubernetes service account permissions used by odh-dashboard for excessive privileges.
- Monitor Kubernetes API activity for unexpected service account token use.
Validation and detection
- Inventory RHOAI versions and odh-dashboard container package builds across clusters.
- Confirm whether affected package versions listed in Red Hat advisories are deployed.
- Check whether odh-dashboard endpoints are reachable by low-privileged authenticated users.
- Review service account bindings and token usage for odh-dashboard namespaces.
- Verify vendor remediation status after applying Red Hat updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-5483 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86redhatCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
8.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- ADP timelineredhat-SADP
Reported to Red Hat.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-03T00:00:00.000Z: Reported to Red Hat.
- 2026-04-10T17:16:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:7397CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:7398CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:7403CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:7404CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-5483CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2454764CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5483.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.