cve.bz

CVE-2026-9798 redhat build of keycloak

4.3 mediumEPSS 0.4%Fix available

Medium (4.3) in redhat build of keycloak. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-305 Authentication Bypass by Primary Weakness
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-9798 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9798?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9798?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9798 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-9798

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-9798](https://cve.bz/cve/badge/CVE-2026-9798.svg)](https://cve.bz/cve/CVE-2026-9798)

HTML:

<a href="https://cve.bz/cve/CVE-2026-9798"><img src="https://cve.bz/cve/badge/CVE-2026-9798.svg" alt="CVE-2026-9798"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.426.4.14-1
Red Hat build of Keycloak 26.426.4-22
Red Hat build of Keycloak 26.626.6.5-1
Red Hat build of Keycloak 26.626.6-11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q6h7-xxp7-7429Mavenorg.keycloak:keycloak-services<=26.4.7no fix published
GHSA-q6h7-xxp7-7429Mavenorg.keycloak:keycloak-services>=26.5.0 <=26.6.4no fix published

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw in Keycloak's Client-Initiated Backchannel Authentication (CIBA) flow is rated as Low impact. The vulnerability allows bypassing brute-force protection when a user account is locked, but only if CIBA is explicitly enabled and configured (non-default), and the user approves the authentication request on their device. This significantly limits the attack surface in typical Red Hat deployments where CIBA is not enabled by default.

Red Hat's mitigation

To mitigate this issue, ensure that Client-Initiated Backchannel Authentication (CIBA) is not enabled in Keycloak realms unless explicitly required. If CIBA is enabled, consider disabling it to prevent the bypass of brute-force protection mechanisms. Consult Keycloak documentation for instructions on managing CIBA configuration.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.14-1Fixed 2026-08-05RHSA-2026:50847
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9:26.4-22Fixed 2026-08-05RHSA-2026:50847
Red Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator:26.4-22Fixed 2026-08-05RHSA-2026:50847
Red Hat build of Keycloak 26.4.14rhbk/keycloak-rhel9Fixed 2026-08-05RHSA-2026:50846
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.5-1Fixed 2026-08-05RHSA-2026:50849
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9:26.6-11Fixed 2026-08-05RHSA-2026:50849
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator:26.6-11Fixed 2026-08-05RHSA-2026:50849
Red Hat build of Keycloak 26.6.5Fixed 2026-08-05RHSA-2026:50848

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-9798.

References

Check your stackJSON