{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-46579 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46579 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46579 is a high-severity authentication bypass vulnerability in Redhat Openshift Container Platform, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46579 and fix it if it is affected.\n\nWhat it is: CVE-2026-46579 is a high-severity authentication bypass vulnerability in Redhat Openshift Container Platform, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46579 in the wild and no public exploit code.\n\nAffected product: Redhat Openshift Container Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46579/ (Markdown: https://insights.sbomify.com/CVE-2026-46579/index.md)","id":"CVE-2026-46579","markdown":"https://insights.sbomify.com/CVE-2026-46579/index.md","name":"CVE-2026-46579","record":{"aliases":["GHSA-ccmj-8c3p-4qwj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenShift Router","requires_auth":"none","summary":"Attackers can bypass mutual TLS authentication by injecting spoofed client certificate headers when insecure edge termination is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"openshift_container_platform","vendor":"redhat"},{"product":"openshift_router","vendor":"redhat"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Red Hat OpenShift Container Platform 4.12","id":"CVE-2026-46579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"[Eclipse Theia] Indirect Prompt Injection via Auto-Loaded Workspace Prompt Template Files in AI Chat","id":"CVE-2026-46580"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-46572"},"products":["Red Hat OpenShift Container Platform 4.12","Red Hat OpenShift Container Platform 4.13","Red Hat OpenShift Container Platform 4.14","Red Hat OpenShift Container Platform 4.15","Red Hat OpenShift Container Platform 4.16","Red Hat OpenShift Container Platform 4.17","Red Hat OpenShift Container Platform 4.18","Red Hat OpenShift Container Platform 4.19","Red Hat OpenShift Container Platform 4.20","Red Hat OpenShift Container Platform 4.21","Red Hat OpenShift Container Platform 4.22"],"published":"2026-05-29","related":[{"cvss_score":9.8,"headline":"Missing authorization in cluster-ingress-operator","id":"CVE-2020-27836","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9,"headline":"Misconfiguration in openshift-ansible","id":"CVE-2018-1085","kev_date_added":null,"published":"2018-06-15"},{"cvss_score":8.8,"headline":"Privilege escalation in Red Hat OpenShift Container Platform 4","id":"CVE-2026-54099","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":8.8,"headline":"Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection","id":"CVE-2026-1784","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":8.8,"headline":"Privilege escalation in openshift","id":"CVE-2021-20182","kev_date_added":null,"published":"2021-02-23"},{"cvss_score":8.8,"headline":"xterm vulnerable to remote code execution","id":"CVE-2019-0542","kev_date_added":null,"published":"2019-01-09"},{"cvss_score":8.5,"headline":"Privilege escalation in source-to-image","id":"CVE-2018-10843","kev_date_added":null,"published":"2018-07-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["Red Hat"]},"summary":"Attackers can bypass mutual TLS authentication by injecting spoofed client certificate headers when insecure edge termination is enabled.","url":"https://insights.sbomify.com/CVE-2026-46579/"}