CVE-2026-9798: Authentication Bypass by Primary Weakness in Red Hat Red Hat build of Keycloak 26.4
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.
AI Analysis
Technical Summary
CVE-2026-9798 is an authentication bypass vulnerability in Red Hat build of Keycloak 26.4 related to the Client-Initiated Backchannel Authentication (CIBA) flow. When a user account is locked due to repeated failed login attempts, an attacker possessing valid client credentials can exploit the CIBA flow to circumvent the brute-force protection mechanism. This flaw allows continued authentication attempts and token issuance even though the account should be locked. The vulnerability is rated with a CVSS 3.1 base score of 4.3 (medium severity) and requires that CIBA be explicitly enabled and configured, which is not the default setting in Red Hat deployments. The user must also approve the authentication request on their device for the bypass to be successful, significantly limiting the practical attack surface.
Potential Impact
The impact is limited to bypassing brute-force protection on locked user accounts via the CIBA flow, potentially allowing continued authentication attempts and token issuance. Confidentiality impact is low, with no integrity or availability impact reported. The vulnerability only affects deployments where CIBA is enabled and configured, which is not the default in Red Hat's Keycloak builds. There are no known exploits in the wild at this time.
Mitigation Recommendations
Red Hat advises ensuring that Client-Initiated Backchannel Authentication (CIBA) is not enabled in Keycloak realms unless explicitly required. If CIBA is enabled, it is recommended to disable it to prevent bypass of brute-force protection. Administrators should consult Keycloak documentation for managing CIBA configuration. No official patch or fix is currently indicated in the advisory; mitigation relies on configuration management.
CVE-2026-9798: Authentication Bypass by Primary Weakness in Red Hat Red Hat build of Keycloak 26.4
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.
CVSS v3.1
Score 4.3medium
Affected software
Red Hat
Red Hat build of Keycloak 26.4
Red Hat
Red Hat build of Keycloak 26.4
Red Hat
Red Hat build of Keycloak 26.4.14
Red Hat
Red Hat build of Keycloak 26.6
Red Hat
Red Hat build of Keycloak 26.6
Red Hat
Red Hat build of Keycloak 26.6.5
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9798 is an authentication bypass vulnerability in Red Hat build of Keycloak 26.4 related to the Client-Initiated Backchannel Authentication (CIBA) flow. When a user account is locked due to repeated failed login attempts, an attacker possessing valid client credentials can exploit the CIBA flow to circumvent the brute-force protection mechanism. This flaw allows continued authentication attempts and token issuance even though the account should be locked. The vulnerability is rated with a CVSS 3.1 base score of 4.3 (medium severity) and requires that CIBA be explicitly enabled and configured, which is not the default setting in Red Hat deployments. The user must also approve the authentication request on their device for the bypass to be successful, significantly limiting the practical attack surface.
Potential Impact
The impact is limited to bypassing brute-force protection on locked user accounts via the CIBA flow, potentially allowing continued authentication attempts and token issuance. Confidentiality impact is low, with no integrity or availability impact reported. The vulnerability only affects deployments where CIBA is enabled and configured, which is not the default in Red Hat's Keycloak builds. There are no known exploits in the wild at this time.
Mitigation Recommendations
Red Hat advises ensuring that Client-Initiated Backchannel Authentication (CIBA) is not enabled in Keycloak realms unless explicitly required. If CIBA is enabled, it is recommended to disable it to prevent bypass of brute-force protection. Administrators should consult Keycloak documentation for managing CIBA configuration. No official patch or fix is currently indicated in the advisory; mitigation relies on configuration management.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-05-28T03:51:03.615Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-9798","vendor":"Red Hat"}]
Threat ID: 6a17daeae29bf47b50b180f2
Added to database: 05/28/2026, 06:04:26 UTC
Last enriched: 08/06/2026, 13:17:06 UTC
Last updated: 09/14/2026, 10:01:34 UTC
Views: 216
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.