cve.bz

CVE-2026-5483 redhat openshift ai

9.9 criticalEPSS 0.5%Fix available

Critical (9.9) in redhat openshift ai. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-201 Insertion of Sensitive Information Into Sent Data
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-5483 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5483?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5483?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-5483 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-5483

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-5483](https://cve.bz/cve/badge/CVE-2026-5483.svg)](https://cve.bz/cve/CVE-2026-5483)

HTML:

<a href="https://cve.bz/cve/CVE-2026-5483"><img src="https://cve.bz/cve/badge/CVE-2026-5483.svg" alt="CVE-2026-5483"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat OpenShift AI 2.161775230902
Red Hat OpenShift AI 2.251775234711
Red Hat OpenShift AI 3.21775523049
Red Hat OpenShift AI 3.31775239958

Red Hat

Red Hat rates this Important.

Red Hat's statement

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

The NIM serving API endpoint (`/api/nim-serving/:nimResource`) returns the full K8 client response including the dashboard's service account token.

Requirements to exploit:

- Authenticated access to the dashboard

- The NIM account CR must exist on the cluster for 2.25+

- The target secret must exist and if the secret referenced by the Account CR hasn't been created yet, the endpoint returns a 404 and no token is leaked

Red Hat's mitigation

If applying the update is not immediately possible, the vulnerability can be mitigated by disabling or removing the NIM (NVIDIA Inference Microservice) integration from the Red Hat OpenShift AI (RHOAI) environment.

ProductPackageStateAdvisory
Red Hat OpenShift AI 2.16rhoai/odh-dashboard-rhel8:1775230902Fixed 2026-04-10RHSA-2026:7397
Red Hat OpenShift AI 2.25rhoai/odh-dashboard-rhel9:1775234711Fixed 2026-04-10RHSA-2026:7398
Red Hat OpenShift AI 3.2rhoai/odh-dashboard-rhel9:1775523049Fixed 2026-04-10RHSA-2026:7404
Red Hat OpenShift AI 3.3rhoai/odh-dashboard-rhel9:1775239958Fixed 2026-04-10RHSA-2026:7403
Red Hat OpenShift AI (RHOAI)rhoai/odh-mod-arch-gen-ai-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-mod-arch-maas-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-mod-arch-model-registry-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-5483.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON