Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-3047 is a high-severity Authentication Bypass by Primary Weakness (CWE-305) vulnerability in Redhat Build Of Keycloak. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-8 (Identification and Authentication (Non-organizational Users)) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-3047 is a high-severity vulnerability (CVSS 8.8) in the org.keycloak.broker.saml component of Keycloak, an open-source identity and access management solution. The flaw occurs when a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target. In this scenario, the disabled client can still complete the login process and establish a Single Sign-On (SSO) session, bypassing intended security restrictions (CWE-305: Improper Restriction of Communication Channel to Intended Endpoints).
A remote attacker with low privileges (PR:L) can exploit this vulnerability over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N). By targeting the misconfigured disabled SAML client, the attacker can establish an unauthorized SSO session, gaining access to other enabled clients without re-authentication. This results in high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), allowing privilege escalation and unauthorized access within the Keycloak environment.
Red Hat has released multiple errata addressing this issue in their Keycloak distributions, including RHSA-2026:3925, RHSA-2026:3926, RHSA-2026:3947, and RHSA-2026:3948. Security practitioners should consult the detailed advisory at https://access.redhat.com/security/cve/CVE-2026-3047 and apply the corresponding patches to mitigate the vulnerability.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9864
Vulnerability Data
A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (SSO) session. This…
more
allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V6.4.3V7.2.4
Mitigating Controls (NIST 800-53 r5) AI
Requires unique identification and authentication of users, structurally blocking bypass of the mechanism.
Requires unique identification and authentication of non-organizational users, blocking bypass paths.
Enforces approved authorizations so a bypass weakness cannot be exploited to reach resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices throughout the SDLC prevent the primary weaknesses that enable authentication bypass.
Strong authentication mechanisms and policy enforcement directly reduce bypass opportunities arising from implementation flaws.
Identifying and recording vulnerabilities catches the primary weaknesses that allow authentication bypass.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect authentication bypass conditions before deployment.
Secure development lifecycle reduces likelihood of introducing bypass flaws during implementation.
Secure coding practices help prevent the primary weakness that enables authentication bypass.
Information access restriction complements authentication by limiting what can be reached even if bypass occurs.
Secure authentication mechanisms directly address bypass risks in the implemented authentication process.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 22.04 (1 rule)
- V-260470 Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes. prevents CWE-305
Ubuntu 24.04 (1 rule)
- V-270675 Ubuntu 24.04 LTS when booted must require authentication upon booting into single-user and maintenance modes. prevents CWE-305