CVE-2026-35563

Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LDAP hostname

Published Jun 1, 2026 CVSS 4.0 · 8.8 High EPSS < 1% KEV · Not listed
Description
It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP
hostname. While the underlying code validates the certificate chain
against a trusted authority, the absence of endpoint identification
allows a valid certificate issued for an entirely unrelated host to be
improperly accepted. This oversight leaves the connection highly
vulnerable to server impersonation and complete connection compromise.


The
root cause of this vulnerability lies in the incomplete TLS server
identity verification within the LDAP client implementation.




The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store.




The hostname verification has been enforced in the new version of the LDAP API

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-85rw-g4f4-jprr Apache Directory LDAP API lacks server certificate verification for LDAP hostnames
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:directory_ldap_api:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache directory Ldap Api
Vendors & Products Apache
Apache directory Ldap Api
Type Values Removed Values Added
Description It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise. The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation. The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store. The hostname verification has been enforced in the new version of the LDAP API
Title Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LDAP hostname
Weaknesses CWE-297
References
Metrics cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:L/SA:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Jun 1, 2026, 1:09 PM
Reserved
Apr 3, 2026, 1:46 PM
Status
Analyzed
Published
Jun 1, 2026, 8:16 AM
Modified
Jul 22, 2026, 7:10 AM