Security readout for executives and security teams
Plain-English summary
A compromised or malicious pod can impersonate users and groups to the MaaS API because the service trusts caller-supplied identity headers. This could expose other tenants’ model credentials, permit service-account token creation, and disrupt API access. The supplied evidence rates the issue critical.
Executive priority
Treat as an urgent tenant-isolation failure. Prioritize affected shared or multi-tenant clusters because one compromised workload could reach another tenant’s credentials and Kubernetes identities. Patch using Red Hat guidance, contain internal API reachability, and investigate for credential misuse.
Technical view
The affected MaaS API trusts X-MaaS-Username and X-MaaS-Group headers without first-party authentication, allowing a low-privileged cluster pod to bypass Kuadrant AuthPolicy. This CWE-290 weakness crosses tenant boundaries and may enable Kubernetes ServiceAccount token minting, API-key revocation, and model-access configuration theft.
Likely exposure
Exposure is limited to deployments containing the affected rhoai/odh-maas-api-rhel9 package for Red Hat OpenShift AI 3.4, identified by the supplied version 1785850409. The two other listed MaaS packages are marked unaffected.
Exploitation context
An attacker requires the ability to operate from a pod inside the cluster, but needs no user interaction and faces low attack complexity. The supplied record is not in KEV and provides no evidence of active exploitation.
Researcher notes
The CVSS 3.1 score is 9.9 with changed scope and high confidentiality, integrity, and availability impact. Evidence identifies header-based authentication bypass from any cluster pod. Exact corrected build numbers and observed exploitation details are not included in the supplied bundle.
Mitigation direction
- Review RHSA-2026:53262 and apply Red Hat’s prescribed security update promptly.
- Restrict pod-to-MaaS API network access until remediation is complete.
- Treat identity headers from untrusted workloads as invalid at every direct API path.
- Rotate potentially exposed model credentials, API keys, and service-account tokens after investigating access.
Validation and detection
- Inventory OpenShift AI 3.4 deployments for rhoai/odh-maas-api-rhel9 version 1785850409.
- Confirm installed builds match the remediated versions specified by RHSA-2026:53262.
- Verify every MaaS API path enforces authenticated identity rather than trusting caller-supplied headers.
- Review audit logs for cross-tenant token creation, API-key revocation, or model-configuration access.
- Confirm unaffected package findings separately; do not infer platform-wide exposure from package names.
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
- 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.