CVE-2026-35563
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
Scoring
- Severity
- HIGH
- CVSS base score
- 8.8
- CVSS 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
- EPSS probability
- 0.18%
- CWE
- CWE-297
- Published
- 2026-06-01
- Last modified
- 2026-06-01
Affected products
- Apache Software Foundation Apache Directory LDAP API
Weakness type
Related vulnerabilities
- CVE-2026-79636 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-84197 — In Eclipse Ditto's Node.js JavaScript client, all released versions of...
- CVE-2026-84393 — A improper validation of certificate with host mismatch vulnerability in Fortinet FortiOS 7.6.1...
- CVE-2026-79943 — Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to...
- CVE-2026-9744 — Vulnerabilities exists in IBM Netezza Software
- CVE-2026-62243 — Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass
- CVE-2026-53583 — libgit2: Inverted IP SubjectAltName Comparison in OpenSSL Backend
- CVE-2026-49457 — QUIC has Broken TLS verification