Cluster user impersonation via unvalidated forwarded token
Published Jul 23, 2026 · Updated Jul 23, 2026
Authentication bypass in Red Hat OpenShift AI 2.25, 3.3, and 3.4 allows remote authenticated users to impersonate any user. The odh-dashboard backend binds to 0.0.0.0:8080 and accepts x-forwarded-access-token without validating that kube-rbac-proxy supplied it. An attacker must control a pod in the cluster; successful impersonation grants the selected user's Kubernetes API permissions, including any associated data access or code-execution privileges.
Summary
What happened
Authentication bypass in Red Hat OpenShift AI 2.25, 3.3, and 3.4 allows remote authenticated users to impersonate any user. The odh-dashboard backend binds to 0.0.0.0:8080 and accepts x-forwarded-access-token without validating that kube-rbac-proxy supplied it. An attacker must control a pod in the cluster; successful impersonation grants the selected user's Kubernetes API permissions, including any associated data access or code-execution privileges.
The record
- CVE
- CVE-2026-16745
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift AI
- Classifications
- CWE-346, CAPEC-21, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo