CVE-2026-3047: Org.keycloak.broker.saml: keycloak saml broker: authentication bypass due to disabled saml client completing idp-initiated login

Published Feb 23, 2026
·
Updated

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.

Other sources

A SAML client marked Disabled in the broker realm still completes IdP-initiated broker login and creates a realm SSO session. Even though the target SAML client is disabled, the user gains a valid Keycloak session and can access other enabled clients without re-authentication. Requirements to exploit

The Keycloak instance must have a disabled SAML client configured as an IdP-initiated broker landing target. The user must also exist in the external IdP.

Red Hat

Affected Software

8 affected components
maven/org.keycloak/keycloak-broker-saml
maven/org.keycloak:keycloak-broker-saml<=1.8.1.Final
redhat Build Of Keycloak
redhat Build Of Keycloak=26.2
redhat Build Of Keycloak=26.2.14
redhat Build Of Keycloak=26.4
redhat Build Of Keycloak=26.4.10
redhat keycloak

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade keycloak/keycloak to a version that resolves this vulnerability.

    Fixed in 26.5.5
  2. Compensating control

    If you cannot upgrade immediately, remove/avoid configuring any disabled SAML client as an IdP-initiated broker landing target, because even a disabled SAML client can still complete IdP-initiated broker login and create a realm SSO session.

Event History

Feb 23, 2026
Data Sourced
via Red Hat·05:33 PM
DescriptionSeverityAffected Software
Mar 5, 2026
CVE Published
via MITRE·06:28 PM
Data Sourced
via MITRE·06:28 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
Affected Software
Advisory Published
via GitHub·09:30 PM
Data Sourced
via GitHub·09:30 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-3047?

The severity of CVE-2026-3047 is considered high due to the possibility of authentication bypass.

2

How does CVE-2026-3047 impact my Keycloak instance?

CVE-2026-3047 allows attackers to bypass authentication by exploiting a disabled SAML client's IdP-initiated login.

3

How do I fix CVE-2026-3047?

To fix CVE-2026-3047, ensure that no disabled SAML clients are configured to act as Identity Providers.

4

What versions of Keycloak are affected by CVE-2026-3047?

CVE-2026-3047 affects versions of Keycloak that utilize the org.keycloak.broker.saml component.

5

Is there a patch available for CVE-2026-3047?

Yes, a patch is available in the latest version of Keycloak to resolve the CVE-2026-3047 vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203