Security readout for executives and security teams
Plain-English summary
A compromised or malicious pod in an affected OpenShift AI cluster can impersonate another user or group. This could cross tenant boundaries, create Kubernetes service-account tokens, revoke API keys, and expose sensitive model-access settings.
Executive priority
Address immediately in affected multi-tenant or less-trusted clusters. The vulnerability can turn one compromised workload into cross-tenant credential and configuration compromise. Confirm affected builds, reduce pod-to-API reachability, apply Red Hat updates, and investigate suspicious activity. Escalation remains urgent despite no supplied evidence of active exploitation.
Technical view
The MaaS API trusts X-MaaS-Username and X-MaaS-Group headers without independently authenticating them. A pod able to reach the API can forge these headers and bypass Kuadrant AuthPolicy protections. This is CWE-290 with CVSS 3.1 score 9.9 because successful abuse can compromise confidentiality, integrity, and availability across security scopes.
Likely exposure
The bundle identifies Red Hat OpenShift AI 3.4 builds 1785850409 and 1787153683 of rhoai/odh-maas-api-rhel9 as affected. Exposure requires a pod inside the cluster that can reach the MaaS API. The listed MaaS controller and modular-architecture MaaS packages are marked unaffected.
Exploitation context
CISA KEV status is false, and the supplied sources do not establish active exploitation or a public exploit. Abuse nevertheless has low complexity once an attacker controls or deploys a pod with network access to the affected API. Treat internal workload compromise as a credible prerequisite, not a complete safeguard.
Researcher notes
The trust-boundary failure is first-party authentication: gateway-provided identity headers remain attacker-controlled when requests originate within the cluster. Validation should focus on whether direct pod-to-API paths preserve or overwrite those headers and whether authorization decisions rely on them. The bundle names two affected builds but does not provide detailed fixed-version data.
Mitigation direction
- Review RHSA-2026:53262 and RHSA-2026:60520, then apply Red Hat's applicable updates.
- Prioritize clusters running either affected rhoai/odh-maas-api-rhel9 build.
- Restrict pod network access to the MaaS API where operationally feasible.
- Rotate exposed credentials or tokens if investigation finds suspected cross-tenant access.
- Consult Red Hat guidance for any additional supported mitigations or upgrade requirements.
Validation and detection
- Inventory OpenShift AI clusters and record installed rhoai/odh-maas-api-rhel9 builds.
- Confirm whether untrusted or tenant pods can reach the MaaS API.
- Review available API and Kubernetes audit logs for unexpected cross-tenant token creation.
- Investigate unexplained API-key revocations or access to model configuration.
- After updating, verify the affected build is absent and authentication controls operate as documented.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-14450 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhatVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:53262CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:60520CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-14450CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2496373CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.