CVE-2026-14450

Maas-billing: maas api: privilege escalation via forged http headers due to missing authentication

Published Aug 10, 2026 CVSS 3.1 · 9.9 Critical EPSS < 1% KEV · Not listed
Description
A flaw was found in the MaaS API. This vulnerability allows any pod within the cluster to bypass the Kuadrant AuthPolicy gateway by forging HTTP headers, specifically `X-MaaS-Username` and `X-MaaS-Group`, which are trusted verbatim. This lack of first-party authentication enables an attacker to gain unauthorized access and escalate privileges. The concrete consequences include the ability to mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and exfiltrate sensitive model access configuration.

Analysis

AI-generated

Technical impact

The vulnerability in the MaaS API allows an attacker to forge HTTP headers X-MaaS-Username and X-MaaS-Group, which the system trusts without further authentication. This lack of first‑party authentication enables an attacker who can generate traffic from any pod in the cluster to bypass the Kuadrant AuthPolicy gateway, granting unauthorized privilege escalation. Consequences include minting Kubernetes ServiceAccount tokens in other tenants’ namespaces, revoking API keys, and exfiltrating model access configuration, thereby compromising confidentiality, integrity, and availability of workloads.

Affected Systems

Red Hat OpenShift AI (RHOAI). No other vendors or product variants are listed as affected.

Risk and Exploitability

With a CVSS score of 9.9, the vulnerability is considered critical. The EPSS score is not available, but the absence of a KEV listing does not reduce its threat; the attack is feasible from any pod in the cluster, requiring the ability to send forged HTTP headers, which is typically achievable by any running container with sufficient network reach to the MaaS API."

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Red Hat OpenShift AI security patch or upgrade to a version that contains the fix.
  • Limit the network paths that allow pods to send traffic to the MaaS API, for example by tightening NetworkPolicy rules.
  • Configure the MaaS API to reject or validate all incoming X-MaaS-Username and X-MaaS-Group headers, ensuring they originate from an authenticated gateway.
  • Rotate or revoke any Kubernetes ServiceAccount tokens or API keys that may have been compromised during the exploitation period.

Generated by OpenCVE AI on August 10, 2026 at 22:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:openshift_ai:3.4::el9
References
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Openshift Ai (rhoai)
Vendors & Products Red Hat
Red Hat red Hat Openshift Ai (rhoai)
Type Values Removed Values Added
Description A flaw was found in the MaaS API. This vulnerability allows any pod within the cluster to bypass the Kuadrant AuthPolicy gateway by forging HTTP headers, specifically `X-MaaS-Username` and `X-MaaS-Group`, which are trusted verbatim. This lack of first-party authentication enables an attacker to gain unauthorized access and escalate privileges. The concrete consequences include the ability to mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and exfiltrate sensitive model access configuration.
Title Maas-billing: maas api: privilege escalation via forged http headers due to missing authentication
First Time appeared Redhat
Redhat openshift Ai
Weaknesses CWE-290
CPEs cpe:/a:redhat:openshift_ai
Vendors & Products Redhat
Redhat openshift Ai
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-290

    Authentication Bypass by Spoofing

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 27, 2026, 3:06 PM
Reserved
Jul 2, 2026, 7:39 AM
Status
Awaiting Analysis
Published
Aug 10, 2026, 9:17 PM
Modified
Aug 27, 2026, 5:17 PM
Severity
Important
Public date
Aug 10, 2026, 6:42 PM