CVE-2026-16071: Keycloak-services: keycloak-services: ldap entry-dn user search bypasses configured users dn boundary

Published Jul 17, 2026
·
Updated

A flaw was found in the LDAP storage provider of Keycloak, which is used to federate user identities from external directories. The issue occurs when a delegated administrator performs a search using a specific LDAP entry Distinguished Name (DN). Due to missing validation, the system allows lookups for users located outside the configured search boundary, leading to the disclosure of account information from unauthorized parts of the directory and unintended importing of those users into local storage.

Other sources

A vulnerability was found in Keycloak where the LDAP storage provider fails to validate the search base during specific entry-DN queries. A delegated administrator with user-query permissions can invoke the admin users endpoint with a crafted query parameter (q=LDAPENTRYDN:target-dn). The LDAP provider replaces the configured users DN with the caller-supplied DN and performs an object-scope lookup. If the target object matches the user schema, Keycloak returns the UserRepresentation and may import the user into local storage. This allows an attacker to bypass organizational unit boundaries within the same LDAP directory to disclose user attributes and metadata for accounts they should not be able to access.

Red Hat

Affected Software

3 affected components
Keycloak Keycloak
redhat Build Of Keycloak>=26.4<26.4.14
redhat Build Of Keycloak>=26.6<26.6.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Keycloak (LDAP storage provider) to a version that resolves this vulnerability.

    Patch Keycloak-services: keycloak-services: ldap entry-dn user search bypasses configured users dn boundary
  2. Compensating control

    Restrict delegated administrator access to the Keycloak admin endpoint that supports the crafted user-query parameter q=LDAP_ENTRY_DN:target-dn (e.g., remove/limit user-query permissions or block access to the relevant admin users endpoint) to prevent search-base/user-DN boundary bypass.

Event History

Jul 17, 2026
Data Sourced
via Red Hat·01:18 PM
DescriptionSeverityAffected Software
Aug 5, 2026
CVE Published
via MITRE·01:50 PM
Data Sourced
via MITRE·01:50 PM
DescriptionSeverity
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-16071?

The severity of CVE-2026-16071 is medium with a score of 5.4.

2

What is the risk associated with CVE-2026-16071?

The risk associated with CVE-2026-16071 is rated at 34.

3

How can I fix CVE-2026-16071?

To mitigate CVE-2026-16071, it is recommended to apply the latest security patch for Keycloak services.

4

What type of attack does CVE-2026-16071 allow?

CVE-2026-16071 allows a delegated administrator to bypass the configured user DN boundary during LDAP entry-DN user searches.

5

Which component of Keycloak is affected by CVE-2026-16071?

CVE-2026-16071 affects the LDAP storage provider component of Keycloak.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203