CVE-2026-46579: Red Hat OpenShift Container Platform 4.12 · Improper Authentication
Affects Red Hat OpenShift Container Platform 4.12Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat OpenShift Container Platform 4.12 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Container Platform 4.13 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Container Platform 4.14 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Container Platform 4.15 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Container Platform 4.16 | Affected– | Fixed in– |
| Red HatRed Hat OpenShift Container Platform 4.17 | Affected– | Fixed in– |
AI-suggested
Red Hat has released fixed versions 4.21.21 and 4.22.2 of OpenShift Container Platform that address this vulnerability. Users should upgrade to these versions as soon as possible using the OpenShift CLI (oc) or web console. Detailed upgrade instructions are available in the Red Hat documentation for OpenShift Container Platform 4.21 and 4.22. No additional mitigations are specified beyond applying the official updates.
Description
A flaw was found in the OpenShift Router. When a Route has `insecureEdgeTerminationPolicy` set to Allow, the HTTP frontend does not remove `X-SSL-Client-*` headers from incoming requests. This allows an unauthenticated attacker to send plain HTTP requests with crafted `X-SSL-Client-*` headers. As a result, backends relying on these headers for mutual TLS (Transport Layer Security) authentication can be bypassed, enabling the attacker to impersonate client certificate identities.
References
- access.redhat.com/errata/RHSA-2026:27009 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:27044 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:27063 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:37580 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:40022 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:40828 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:43227 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:43253 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:43331 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-46579 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2483181 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46579.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:47728 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:47703 (opens in a new tab)