Description
A flaw was found in Keycloak, an open-source identity and access management solution. When a user account is temporarily locked due to repeated failed login attempts, an attacker with valid client credentials can exploit the Client-Initiated Backchannel Authentication (CIBA) flow to bypass this brute-force protection. This allows continued authentication attempts and token issuance even when the account should be locked, potentially enabling further unauthorized access attempts.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.14-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-22 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-22 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.14
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6.5-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-11 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-11 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6.5
Default version status: unaffected
References
- https://access.redhat.com/errata/RHSA-2026:50846 ↗
- https://access.redhat.com/errata/RHSA-2026:50847 ↗
- https://access.redhat.com/errata/RHSA-2026:50848 ↗
- https://access.redhat.com/errata/RHSA-2026:50849 ↗
- https://access.redhat.com/security/cve/CVE-2026-9798 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2482470 ↗