No advisories yet.
Solution
No solution given by the vendor.
Workaround
To mitigate this issue, ensure that any SAML client intended to be disabled is not configured as an IdP-initiated broker landing target within Keycloak. Review your Keycloak realm configurations to identify and remove any such associations for disabled clients.
Thu, 05 Mar 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:build_keycloak:26.2::el9 | |
| References |
|
Thu, 05 Mar 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:build_keycloak:26.4::el9 | |
| References |
|
Thu, 05 Mar 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Org.keycloak.broker.saml: keycloak saml broker: authentication bypass due to disabled saml client completing idp-initiated login | |
| First Time appeared |
Redhat
Redhat build Keycloak |
|
| Weaknesses | CWE-305 | |
| CPEs | cpe:/a:redhat:build_keycloak: | |
| Vendors & Products |
Redhat
Redhat build Keycloak |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-03-05T19:57:26.672Z
Reserved: 2026-02-23T17:30:53.926Z
Link: CVE-2026-3047
No data.
Status : Awaiting Analysis
Published: 2026-03-05T19:16:18.383
Modified: 2026-03-05T20:16:17.137
Link: CVE-2026-3047
No data.
OpenCVE Enrichment
No data.