Skip to main content
VulnerabilityPublished Updated

CVE-2026-14450: Red Hat OpenShift AI 3.4 · Authentication Bypass by Spoofing

Affects Red Hat OpenShift AI 3.4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI (RHOAI)Affected–Fixed in–

AI-suggested

Until a fix is available, consider restricting pod permissions and network policies to limit the ability to forge HTTP headers and access the MaaS API. Engage with Red Hat Technical Account Managers if available for tailored mitigation advice.

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.

References

Community reviews

Loading reviews…