CVE-2026-3009: Org.keycloak/keycloak-services: improper enforcement of disabled identity provider in identitybrokerservice (authentication bypass)

Published Feb 23, 2026
·
Updated

A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using an Identity Provider (IdP) even after it has been disabled by an administrator. An attacker who knows the IdP alias can reuse a previously generated login request to bypass the administrative restriction. This undermines access control enforcement and may allow unauthorized authentication through a disabled external provider.

Other sources

Improper Authorization vulnerability in the IdentityBrokerService.performLogin endpoint of the Keycloak services component. The flaw occurs because the broker login endpoint does not re-validate the enabled/disabled status of the configured Identity Provider (IdP) at the time of login processing. If a valid authentication flow is initiated before the IdP is disabled, an attacker who knows the broker alias can manually invoke the broker login URL (/realms/{realm}/broker/{alias}/login) with valid session parameters. Despite the IdP being administratively disabled, the authentication flow proceeds and redirects the user to the external provider. This allows authentication via a disabled IdP, effectively bypassing administrative access control restrictions. The issue can be exploited remotely without privileges but requires user interaction and knowledge of the IdP alias.

Red Hat

Affected Software

8 affected componentsFixes available
maven/org.keycloak/keycloak-services
maven/org.keycloak:keycloak-services<26.5.5
26.5.5
redhat Build Of Keycloak
redhat Build Of Keycloak=26.4
redhat Build Of Keycloak=26.4.10
redhat JBoss Enterprise Application Platform=8.0
redhat Jboss Enterprise Application Platform Expansion Pack
redhat Single Sign-on=7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.5.5

Event History

Feb 23, 2026
Data Sourced
via Red Hat·05:23 AM
DescriptionSeverityAffected Software
Mar 5, 2026
CVE Published
via MITRE·06:27 PM
Data Sourced
via MITRE·06:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected 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-3009?

CVE-2026-3009 has a high severity rating due to its potential for allowing unauthorized authentication.

2

How do I fix CVE-2026-3009?

To fix CVE-2026-3009, upgrade the Keycloak services to version 26.5.5 or higher.

3

What type of vulnerability is CVE-2026-3009?

CVE-2026-3009 is categorized as an authentication bypass vulnerability.

4

Which software is affected by CVE-2026-3009?

CVE-2026-3009 affects the Keycloak services package, specifically the org.keycloak:keycloak-services.

5

What is the impact of CVE-2026-3009?

The impact of CVE-2026-3009 allows attackers to authenticate via disabled identity providers, undermining security.

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