{"id":"CVE-2026-35563","aliases":["DEBIAN-CVE-2026-35563","EUVD-2026-33569","GHSA-85rw-g4f4-jprr","UBUNTU-CVE-2026-35563"],"status":"published","title":"Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LDAP hostname","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 \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\n\n\n\nThe 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.\n\n\n\n\nThe hostname verification has been enforced in the new version of the LDAP API","severity":{"version":"4.0","score":8.8,"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","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00182,"percentile":0.07781,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-297"],"published":"2026-06-01T07:12:05Z","modified":"2026-11-10T04:00:08Z","fixes":[{"ecosystem":"Maven","package":"org.apache.directory.api:api-ldap-client-api","fixed_in":["2.1.8"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"apache-directory-api","fixed_in":["2.1.9-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.directory.api:api-ldap-client-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.1.8"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-1","2.1.2-2","2.1.9-1"]},{"source":"osv","ecosystem":"Debian:13","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-2","2.1.9-1"]},{"source":"osv","ecosystem":"Debian:14","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.9-1"}]}],"versions":["2.1.2-2"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.directory.api:api-ldap-client-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.1.8"}]}],"versions":["2.0.0","2.0.0.AM1","2.0.0.AM2","2.0.0.AM3","2.0.0.AM4","2.0.1","2.0.2","2.1.0","2.1.1","2.1.2","2.1.3","2.1.4","2.1.5","2.1.6","2.1.7"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0.0~M20-3"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0.0~M20-5","1.0.0-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0.0-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0.0-2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-2build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"apache-directory-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.1.2-2","2.1.2-2build1"]}],"products":[{"vendor":"apache","product":"directory_ldap_api"},{"vendor":"apache software foundation","product":"apache directory ldap api"}],"references":[{"url":"https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nn","tags":["vendor-advisory","Mailing List","Vendor Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2026/06/01/2","tags":["Mailing List","Third Party Advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35563","tags":["advisory"]},{"url":"https://github.com/apache/directory-ldap-api/commit/57a7726d8b6436c74945c12f5ba4e12d232d2bac","tags":["web"]},{"url":"https://github.com/advisories/GHSA-85rw-g4f4-jprr"},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/35xxx/CVE-2026-35563.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-35563","tags":["advisory"]},{"url":"https://github.com/apache/directory-ldap-api","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-35563","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-35563","tags":["report"]},{"url":"https://www.openwall.com/lists/oss-security/2026/06/01/2","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-35563","title":"Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LDAP hostname","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 \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\n\n\n\nThe 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.\n\n\n\n\nThe hostname verification has been enforced in the new version of the LDAP API","status":"published","published":"2026-06-01T07:12:05.815Z","modified":"2026-06-01T13:09:55.143Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high","assessor":"cna"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T14:20:05.15083Z"}],"euvd":[{"id":"EUVD-2026-33569","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 \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\n\n\n\nThe 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.\n\n\n\n\nThe hostname verification has been enforced in the new version of the LDAP API","status":"published","published":"2026-06-01T07:12:05Z","modified":"2026-06-01T13:09:55Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high"}],"updated_at":"2026-11-02T18:20:58.729223Z"}],"ghsa":[{"id":"GHSA-85rw-g4f4-jprr","title":"Apache Directory LDAP API lacks server certificate verification for LDAP hostnames","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.\n\nThe root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.\n\nThe 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.\n\nThe hostname verification has been enforced in the new version of the LDAP API.","status":"published","published":"2026-06-01T09:31:11Z","modified":"2026-07-07T23:46:50Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T14:40:40.389795Z"}],"nvd":[{"id":"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 \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\n\n\n\nThe 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.\n\n\n\n\nThe hostname verification has been enforced in the new version of the LDAP API","status":"published","published":"2026-06-01T08:16:20.307Z","modified":"2026-07-22T07:10:00.107Z","cvss":[{"version":"4.0","score":8.8,"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T14:12:21.635958Z"}],"osv":[{"id":"CVE-2026-35563","title":"Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LDAP hostname","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 \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\n\n\n\nThe 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.\n\n\n\n\nThe hostname verification has been enforced in the new version of the LDAP API","status":"published","published":"2026-06-01T07:12:05.815Z","modified":"2026-10-28T02:31:07.461440073Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T15:45:02.673625Z"},{"id":"DEBIAN-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","status":"published","published":"2026-06-01T08:16:20.307Z","modified":"2026-11-10T04:00:08.501193897Z","cvss":[{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-10T04:22:10.004764Z"},{"id":"GHSA-85rw-g4f4-jprr","title":"Apache Directory LDAP API lacks server certificate verification for LDAP hostnames","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.\n\nThe root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.\n\nThe 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.\n\nThe hostname verification has been enforced in the new version of the LDAP API.","status":"published","published":"2026-06-01T09:31:11Z","modified":"2026-07-08T00:11:30.84857Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high"}],"cwes":["CWE-297"],"updated_at":"2026-11-02T15:46:41.732368Z"},{"id":"UBUNTU-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","status":"published","published":"2026-06-01T08:16:00Z","modified":"2026-10-17T12:58:13.438068748Z","cvss":[{"version":"4.0","score":8.8,"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","level":"high"},{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:56:16.686388Z"}]}}