Vulnerability 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
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Directory Ldap Api | >= 2.0.0, < 2.1.7 |
Related Weaknesses (CWE)
References
- https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nnMailing ListVendor Advisory
- http://www.openwall.com/lists/oss-security/2026/06/01/2Mailing ListThird Party Advisory
FAQ
What is CVE-2026-35563?
CVE-2026-35563 is a vulnerability with a CVSS score of 8.5 (HIGH). 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 certificat...
How severe is CVE-2026-35563?
CVE-2026-35563 has been rated HIGH with a CVSS base score of 8.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-35563?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Directory Ldap Api.