Keycloak SAML Broken has Authentication Bypass by Primary Weakness
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. A fix is available at https://github.com/keycloak/keycloak/releases/tag/26.5.5.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-3047US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:3925WEB
- https://access.redhat.com/errata/RHSA-2026:3926WEB
- https://access.redhat.com/errata/RHSA-2026:3947WEB
- https://access.redhat.com/errata/RHSA-2026:3948WEB
- https://access.redhat.com/security/cve/CVE-2026-3047WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2441966WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/releases/tag/26.5.5WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan