Description
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 allows a remote attacker to gain unauthorized access to other enabled clients without re-authentication, effectively bypassing security restrictions.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2.14-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-16 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2
Default version status: affected
26.2-16 to < *unaffected
Red Hat Red Hat build of Keycloak 26.2.14
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.10-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.10
Default version status: unaffected
References
- https://access.redhat.com/errata/RHSA-2026:3925 ↗
- https://access.redhat.com/errata/RHSA-2026:3926 ↗
- https://access.redhat.com/errata/RHSA-2026:3947 ↗
- https://access.redhat.com/errata/RHSA-2026:3948 ↗
- https://access.redhat.com/security/cve/CVE-2026-3047 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2441966 ↗
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3047.json ↗