CVE-2026-35563Apache · Directory_ldap_api
Vulnerability data via NVD (ingested)
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
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
vuln:CVE-2026-35563product:"Apache Directory Ldap Api"http.html:"Directory Ldap Api"More intel sources (5)
vuln:CVE-2026-35563vulnerabilities.cve_id: CVE-2026-35563CVE-2026-35563CVE-2026-35563"CVE-2026-35563" exploit -site:nvd.nist.gov