CVE-2026-5483 is a high-severity information disclosure vulnerability in the odh-dashboard component of Red Hat OpenShift AI (RHOAI). The flaw is caused by a NodeJS endpoint in odh-dashboard returning Kubernetes Service Account tokens to unauthorized actors without properly stripping or redacting sensitive authentication material. Because Kubernetes Service Account tokens can be used to authenticate directly to the Kubernetes API server, disclosure of these tokens can expose cluster resources to unauthorized access. The provided material does not disclose the exact vulnerable endpoint path or the complete affected version range, but identifies the issue as affecting odh-dashboard in RHOAI and classifies it as CWE-201.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information disclosure vulnerability in the odh-dashboard component of Red Hat OpenShift AI that can expose Kubernetes Service Account tokens via a NodeJS endpoint, potentially enabling unauthorized access to Kubernetes resources.
A sensitive information exposure vulnerability in the odh-dashboard component of Red Hat OpenShift AI where a NodeJS endpoint returns Kubernetes Service Account tokens to unauthorized users, potentially enabling direct Kubernetes API access and cluster resource compromise.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.