Bug 2496373 (CVE-2026-14450) - CVE-2026-14450 maas-billing: MaaS API: Privilege escalation via forged HTTP headers due to missing authentication
Summary: CVE-2026-14450 maas-billing: MaaS API: Privilege escalation via forged HTTP h...
Keywords:
Status: NEW
Alias: CVE-2026-14450
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-02 07:21 UTC by OSIDB Bzimport
Modified: 2026-08-10 18:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-02 07:21:33 UTC
maas-api performs no first-party authentication. The sole identity source for every protected route (/v1/tokens, /v1/api-keys, /v1/models) is the ExtractUserInfo() gin middleware, which reads X-MaaS-Username and X-MaaS-Group HTTP headers and trusts them verbatim. Without a NetworkPolicy restricting direct pod access, any pod in the cluster can bypass the Kuadrant AuthPolicy gateway and forge requests as any user — minting Kubernetes ServiceAccount tokens (TokenRequest) in other tenants' namespaces, revoking their API keys, and exfiltrating their model access configuration.


Note You need to log in before you can comment on or make changes to this bug.