CVE-2026-35563

The record

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

Affected packages

Related vulnerabilities

• CVE-2026-88647 A hostname verification bypass in GnuTLS v3.8.13 allows attackers to circumvent the… CWE-297
• CVE-2026-107660 FFmpeg before 8.1.3 and 9.x before 9.0.2 contains an improper certificate validation… CWE-297
• CVE-2026-19553 ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if… CWE-297
• CVE-2026-91769 PHP's OpenSSL stream peer verification checks the certificate's subjectAltName entries… CWE-297
• CVE-2026-63374 AnyIO is a high level asynchronous concurrency and networking framework that works on top… CWE-297
• CVE-2026-79636 Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions… CWE-297
• CVE-2026-84197 In Eclipse Ditto's Node.js JavaScript client, all released versions of… CWE-297
• CVE-2026-9744 IBM Netezza Software 11.3.0.3 through Interim Fix 002 does not validate or improperly… CWE-297