Bug 2514529 (CVE-2026-19607) - CVE-2026-19607 keycloak-services: keycloak-services: Broker-originated username collision causes account lockout
Summary: CVE-2026-19607 keycloak-services: keycloak-services: Broker-originated userna...
Keywords:
Status: NEW
Alias: CVE-2026-19607
Deadline: 2026-11-09
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-12 08:42 UTC by OSIDB Bzimport
Modified: 2026-09-16 13:27 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-12 08:42:39 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.