CVE-2026-14450

Received Received - Intake

MaaS API Header Forgery Leads to Privilege Escalation

Publication date: 2026-08-10

Last updated on: 2026-08-10

Assigner: Red Hat, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-08-10

Generated

2026-08-11

AI Q&A

2026-08-11

EPSS Evaluated

N/A

NVD

CVE-2026-14450

Affected Vendors & Products

Vendor	Product	Version / Range
redhat	maas	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-290	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

Executive Summary

This vulnerability is in the MaaS API where any pod in the cluster can bypass the Kuadrant AuthPolicy gateway by forging HTTP headers like X-MaaS-Username and X-MaaS-Group. This allows unauthorized access and privilege escalation within the Kubernetes environment.

Impact Analysis

An attacker could exploit this to gain unauthorized access, mint Kubernetes ServiceAccount tokens in other tenants' namespaces, revoke API keys, and steal sensitive model access configurations. This could lead to data breaches or system compromise.

Compliance Impact

This vulnerability could lead to unauthorized access and data exfiltration, violating confidentiality requirements in GDPR and HIPAA. Organizations may face compliance violations, legal penalties, and reputational damage due to compromised sensitive data.

Mitigation Strategies

Immediately update MaaS API to the latest patched version to address the header forgery issue. Review and restrict pod permissions to prevent unauthorized access to the cluster. Monitor network traffic for suspicious HTTP headers like X-MaaS-Username and X-MaaS-Group.

Hi! I’m here to help you understand CVE-2026-14450. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70