GPU VulnDB

Database/AI/ML frameworks & serving

OpenShift AI dashboard: unauthorized Secret read exposes the cluster NGC API key and NIM pull secret

CVSS 6.5CVE-2026-86332AI/ML frameworks & servingcurated

Impact

The dashboard's backend-for-frontend reads Kubernetes Secrets with its own service account and returns the whole object including .data, with no authorization check on the read path - create and delete of the same NIM credential are admin-gated, the read is not. Any authenticated dashboard user, including a data scientist with a single project, retrieves the cluster-wide NVIDIA NGC API key and the NIM image pull secret. Those are org-level credentials for pulling entitled NVIDIA inference containers and models, so the blast radius is the whole NGC entitlement, not one namespace. Red Hat states this is distinct from CVE-2026-5483 (service-account token leak on the same route) and CVE-2026-16456.

Who can reach it

Network reach to the OpenShift AI dashboard route plus any valid dashboard login. No admin role, no cluster RBAC on Secrets needed.

What to do

Track the Red Hat advisory for the fixed odh-dashboard build - the record names no fixed version yet. Independently of patching, treat the NGC API key and the NIM pull secret as disclosed and rotate them, because every dashboard user who existed while the route was live could have read them. Rotation is the part that cannot wait for a maintenance window; the dashboard update itself is a rolling deployment with no node impact.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.