CVE-2026-9801 json
Keycloak: keycloak: denial of service via malformed ldap password policy response
published 5mo ago modified 16d ago also GHSA-f6r7-6w34-x2gp , EUVD-2026-32718
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
A flaw was found in Keycloak. A remote attacker with high privileges, such as a realm administrator configuring a malicious Lightweight Directory Access Protocol (LDAP) server or an attacker compromising an upstream LDAP server, could exploit this vulnerability. By sending a malformed LDAP password policy response during a password authentication request, the attacker can trigger an OutOfMemoryError. This causes the Keycloak Java Virtual Machine (JVM) to terminate, leading to a denial of service (DoS) for all realms on the affected node.
Patch / fix
- maven org.keycloak:keycloak-ldap-federation 26.6.3
- Red Hat Red Hat build of Keycloak 26.4 26.4-19, 26.4.13-1
- Red Hat Red Hat build of Keycloak 26.6 26.6-6, 26.6.3-3
- github.com/keycloak/keycloak@2c4fe42 commit
- github.com/keycloak/keycloak#49514 pull request
Is CVE-2026-9801 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-9801 updated cvss 4.9
keycloak: Keycloak: Denial of Service via malformed LDAP password policy response
-
Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-19, rhbk/keycloak-rhel9-operator 26.4-19, rhbk/keycloak-operator-bundle 26.4.13-1fixed: vendor fix RHSA-2026:30050
-
Red Hat build of Keycloak 26.4.13fixed: vendor fix RHSA-2026:30049
-
Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-6, rhbk/keycloak-rhel9-operator 26.6-6, rhbk/keycloak-operator-bundle 26.6.3-3fixed: vendor fix RHSA-2026:25097
-
Red Hat build of Keycloak 26.6.3fixed: vendor fix RHSA-2026:25098
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-ldap-federation | <26.6.3 |
26.6.3 |
Affected products
- Red Hat Red Hat build of Keycloak 26.4
- Red Hat Red Hat build of Keycloak 26.4.13
- Red Hat Red Hat build of Keycloak 26.6
- Red Hat Red Hat build of Keycloak 26.6.3
Classification
- Weakness
-
- CWE-1284 Improper Validation of Specified Quantity in Input
References
-
github.com
/keycloak/keycloak/pull/49514
web
-
github.com
/keycloak/keycloak/commit/2c4fe42235ba8c265b1da3a30541a270d5bd8c39
web
-
access.redhat.com
/errata/RHSA-2026:25097
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2026:25098
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2026:30049
vendor-advisory, web
-
access.redhat.com
/errata/RHSA-2026:30050
vendor-advisory, web
-
access.redhat.com
/security/cve/CVE-2026-9801
vdb-entry, web, mitigation, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2482473
issue-tracking, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-9801
advisory
-
github.com
/keycloak/keycloak/issues/49434
web
-
github.com
/keycloak/keycloak
package
Sources
- CVE List CVE-2026-9801
- GitHub Advisory GHSA-f6r7-6w34-x2gp
- NVD CVE-2026-9801
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.