CVE-2026-19607: Keycloak-services: keycloak-services: broker-originated username collision causes account lockout

Published Aug 12, 2026
·
Updated

A flaw was found in the first-broker-login flow of the keycloak-services component. This component handles the initial authentication and account linking when a user logs in via an external identity provider. The issue allows an attacker to register a matching username on an external provider to trigger a collision in Keycloak, which results in the legitimate user being locked out of their account.

Other sources

A flaw was found in the Keycloak first-broker-login flow within the keycloak-services Maven artifact. The vulnerability exists because the flow does not sufficiently validate or prevent a brokered identity from colliding with an existing local user's username when loginWithEmail is enabled and usernames are email-shaped. An unauthenticated remote attacker can register an account on a configured external Identity Provider using an email address that matches a victim's Keycloak username. By performing a broker login with this account, the attacker creates a username collision state. This state causes all subsequent authentication attempts by the legitimate victim to fail, effectively locking them out of their account.

— Red Hat

Affected Software

1 affected component
maven/org.keycloak/keycloak-services

Event History

Aug 12, 2026
Data Sourced
via Red Hat·08:42 AM
DescriptionSeverityAffected Software
Sep 16, 2026
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Keycloak configurations are affected?

Affected deployments use a configured external identity provider, have loginWithEmail enabled, and use usernames in an email-shaped format. The issue occurs during the first-broker-login and account-linking flow.

2

What does an attacker need to exploit this issue?

The attacker does not need to authenticate to Keycloak. They need to register an account with the configured external identity provider using an email address that matches a victim's Keycloak username, then perform a broker login.

3

What is the practical impact on a targeted user?

A successful broker login creates a username-collision state. Subsequent authentication attempts by the legitimate user fail, locking that user out of their account.

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