Cross-tenant privilege escalation via forged identity headers
Published Aug 10, 2026 · Updated Aug 10, 2026
Authentication bypass in Red Hat OpenShift AI 3.4 allows remote authenticated users to gain cross-tenant privileges through forged headers. The MaaS API trusts X-MaaS-Username and X-MaaS-Group verbatim instead of authenticating requests independently of the Kuadrant AuthPolicy gateway. Control of any cluster pod is required; successful requests can mint ServiceAccount tokens in other namespaces, revoke API keys, and read model-access configuration.
Summary
What happened
Authentication bypass in Red Hat OpenShift AI 3.4 allows remote authenticated users to gain cross-tenant privileges through forged headers. The MaaS API trusts X-MaaS-Username and X-MaaS-Group verbatim instead of authenticating requests independently of the Kuadrant AuthPolicy gateway. Control of any cluster pod is required; successful requests can mint ServiceAccount tokens in other namespaces, revoke API keys, and read model-access configuration.
The record
- CVE
- CVE-2026-14450
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift AI
- Classifications
- CWE-290
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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