CVE-2026-9801: Keycloak: keycloak: denial of service via malformed ldap password policy response
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-9801 is a denial-of-service flaw in Red Hat build of Keycloak. A highly privileged attacker, or someone controlling an upstream LDAP server, can send a malformed LDAP password policy response that crashes the Keycloak JVM. This can make all realms on the affected node unavailable.
Executive priority
Treat as a timely availability fix for identity infrastructure, not an emergency internet-wide compromise. Prioritize if Keycloak supports critical applications or shared realms, because one affected node crash can disrupt authentication service for users.
Technical view
Keycloak mishandles malformed LDAP password policy responses during password authentication, causing an OutOfMemoryError and JVM termination. The CVSS 3.1 score is 4.9 with network reachability, low attack complexity, high privileges required, no confidentiality or integrity impact, and high availability impact.
Likely exposure
Exposure is limited to affected Red Hat build of Keycloak 26.4 and 26.6 deployments using LDAP integration, especially where realm administrators can configure LDAP or where an upstream LDAP server could be compromised.
Exploitation context
Sources do not report active exploitation, and this CVE is not listed as KEV in the provided bundle. The attack requires high privileges or control of an upstream LDAP server, reducing likelihood but leaving meaningful outage risk.
Researcher notes
The key constraint is attacker position: high-privileged realm administrator or compromised/malicious LDAP server. Public sources describe impact and affected Red Hat builds but do not provide exploit details. Focus validation on version state, LDAP integration, administrative boundaries, and JVM crash indicators.
Mitigation direction
Review the relevant Red Hat advisories for fixed packages and upgrade guidance.
Prioritize affected Keycloak nodes integrated with LDAP identity stores.
Restrict who can configure realm LDAP providers.
Review trust and administrative control of upstream LDAP servers.
Use vendor guidance if your exact package status is unclear.
Validation and detection
Inventory Red Hat build of Keycloak versions and package releases.
Compare installed packages against Red Hat advisory affected and unaffected status.
Identify realms using LDAP federation or LDAP authentication flows.
Check logs for OutOfMemoryError events and unexpected JVM restarts.
Confirm patched nodes remain stable during normal LDAP authentication.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1284: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1284 · source CWE mapping
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.