# CVE-2026-9801: Keycloak: keycloak: denial of service via malformed ldap password policy response

> A remote attacker with high privileges can cause a denial of service by triggering an OutOfMemoryError via a malformed LDAP response.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 26 Jun 2026
- **Also known as:** ECHO-3411-bdf5-a850, GHSA-f6r7-6w34-x2gp, MINI-2qh8-39g9-2wxh, MINI-qhfc-6h7f-hmxc

## What is CVE-2026-9801?

CVE-2026-9801 is a medium-severity denial of service vulnerability in Redhat Build of Keycloak, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2026-9801?

2 open source packages ship an affected version, including org.keycloak:keycloak-ldap-federation. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-ldap-federation` | Maven | All versions | 26.6.3 |
| `org.keycloak:keycloak-ldap-federation` | Maven | All versions | 26.6.3 |

Products: Redhat Build of Keycloak.

## How do I fix CVE-2026-9801?

Upgrade org.keycloak:keycloak-ldap-federation to 26.6.3 or later.

## Is CVE-2026-9801 being exploited?

There is no known exploitation of CVE-2026-9801 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9801 and fix it if it is affected.

What it is: CVE-2026-9801 is a medium-severity denial of service vulnerability in Redhat Build of Keycloak, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9801 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 26.6.3
- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 26.6.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9801/ (Markdown: https://insights.sbomify.com/CVE-2026-9801/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9801
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9801
- OSV: https://osv.dev/vulnerability/CVE-2026-9801

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9801/
Summaries are generated and may contain mistakes; the official description above is the record.