Title: Apache Directory LDAP API de Apache Software Foundation, Description: Se identificó que la implementación del cliente LDAP en la versión 2.1.7 no verifica si el certificado del servidor coincide con el nombre de host LDAP previsto. Si bien el código subyacente valida la cadena de certificados contra una autoridad de confianza, la ausencia de identificación de punto final permite que un certificado válido emitido para un host completamente no relacionado sea aceptado incorrectamente. Esta omisión deja la conexión altamente vulnerable a la suplantación del servidor y al compromiso completo de la conexión.

La causa raíz de esta vulnerabilidad reside en la verificación incompleta de la identidad del servidor TLS dentro de la implementación del cliente LDAP.

El atacante requiere capacidad de MitM en la red para explotar esta vulnerabilidad. Este atacante debe poder presentar un certificado de confianza para el almacén de confianza configurado del cliente.

La verificación del nombre de host se ha aplicado en la nueva versión de la API LDAP.

{"timestamp":"2026-06-01T13:09:38.839628Z","id":"CVE-2026-35563","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}

[{"vendor":"Apache Software Foundation","product":"Apache Directory LDAP API","defaultStatus":"unaffected","collectionURL":"https://repo.maven.apache.org/maven2","packageName":"org.apache.directory.api:api-ldap-client-api","versions":[{"version":"2.0.0","lessThanOrEqual":"2.1.7","versionType":"maven","status":"affected"}]}]

AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

OR
          *cpe:2.3:a:apache:directory_ldap_api:*:*:*:*:*:*:*:* versions from (including) 2.0.0 up to (excluding) 2.1.7

Apache Software Foundation: https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nn Types: Mailing List, Vendor Advisory

CVE: http://www.openwall.com/lists/oss-security/2026/06/01/2 Types: Mailing List, Third Party Advisory

http://www.openwall.com/lists/oss-security/2026/06/01/2

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

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

CWE-297

https://lists.apache.org/thread/5rc2nzqxp1m9wknyf93r8dnp46fhc1nn