dbcve.org
Openshift AiApplication · Redhat

CVE-2026-5483

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-10
Fix available
A fix is available. Upgrade to 2.16.4 / 2.25.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical vulnerability in odh-dashboard (Red Hat OpenShift AI) allows unauthorized disclosure of Kubernetes Service Account tokens through an exposed NodeJS endpoint. Attackers exploiting this flaw can obtain valid tokens and gain privileged access to Kubernetes resources within the cluster.

MitigationImmediately restrict network access to the odh-dashboard component, rotate any potentially compromised Service Account tokens, and apply vendor-provided patches or upgrades to odh-dashboard. Audit all Service Accounts and their permissions as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift AiApplication
Affected:>= 2.16, < 2.16.4>= 2.25, < 2.25.4= 3.2= 3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Red Hat OpenShift AI version
    Run 'oc get clusterversion' or query the OpenShift AI operator version in the 'redhat-ods-operator' namespace using 'oc get operands -n redhat-ods-operator'
    Affected if Version falls within >= 2.16 and < 2.16.4, OR >= 2.25 and < 2.25.4, OR equals 3.2, OR equals 3.3
  2. Confirm odh-dashboard component is deployed
    Run 'oc get pods -A | grep odh-dashboard' or 'oc get deployment -A -l app.kubernetes.io/name=odh-dashboard'
    Affected if odh-dashboard pods or deployments exist in the cluster
  3. Check odh-dashboard network accessibility
    Run 'oc get route -A | grep odh-dashboard' and 'oc get svc -A | grep odh-dashboard' to identify external access points
    Affected if odh-dashboard is exposed via a Route or external Service, allowing network access from outside the cluster

A user is affected if they run a vulnerable Red Hat OpenShift AI version AND have odh-dashboard deployed and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.16.4 / 2.25.4 or later
Fixed in 2.16.42.25.4
Interim mitigation

Immediately restrict network access to the odh-dashboard component, rotate any potentially compromised Service Account tokens, and apply vendor-provided patches or upgrades to odh-dashboard. Audit all Service Accounts and their permissions as a precautionary measure.

Recommended fix High confidence

OpenShift AI 2.16.4+ (2.16 branch), 2.25.4+ (2.25 branch), or 3.4+ (3.x branch)

  1. Identify the currently installed OpenShift AI version using `oc get dashboard odh-dashboard -n redhat-ods-applications` or the ODH dashboard UI
  2. For OpenShift AI 2.16.x deployments: Upgrade to version 2.16.4 or later by following the ODH Dashboard upgrade documentation
  3. For OpenShift AI 2.25.x deployments: Upgrade to version 2.25.4 or later by following the ODH Dashboard upgrade documentation
  4. For OpenShift AI 3.x deployments: Upgrade to version 3.4 or later (the next release after 3.3)
  5. After upgrade, verify the odh-dashboard component is running the patched version by checking the container image tag
  6. Validate that the NodeJS endpoint no longer exposes Kubernetes Service Account tokens by testing the affected endpoint
Caveat Standard OpenShift AI upgrade procedures apply - ensure backup of ODH configurations and review upgrade pre-requisites in Red Hat documentation before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Ai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5483 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data