CVE-2026-35563
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
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.apache.directory.api:api-ldap-client-apiMaven | >= 2.0.0, < 2.1.8 | 2.1.8 |
Affected products
3= 2.1.7+ 1 more
- (no CPE)range: = 2.1.7
- cpe:2.3:a:apache:directory_ldap_api:*:*:*:*:*:*:*:*range: >=2.0.0,<2.1.7
- Range: <2.1.7
Patches
Vulnerability mechanics
References
5- www.openwall.com/lists/oss-security/2026/06/01/2nvdMailing ListThird Party AdvisoryWEB
- github.com/advisories/GHSA-85rw-g4f4-jprrghsaADVISORY
- lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nnnvdMailing ListVendor AdvisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2026-35563ghsaADVISORY
- github.com/apache/directory-ldap-api/commit/57a7726d8b6436c74945c12f5ba4e12d232d2bacghsaWEB
News mentions
0No linked articles in our index yet.