https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 20:46:34 +0000 https://cve.radiocsirt.org/vuln/cleanstart-2026-eu32419 <p><strong>Affected:</strong> CleanStart: keycloak</p> <p>Security vulnerability affects the keycloak package. It was identified that the LDAP client implementation in version 2.</p> <p><strong>Affected:</strong> CleanStart: keycloak</p> <p>Security vulnerability affects the keycloak package. It was identified that the LDAP client implementation in version 2.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-eu32419 https://cve.radiocsirt.org/vuln/euvd-2026-323317 EUVD-2026-323317 https://cve.radiocsirt.org/vuln/euvd-2026-323317 https://cve.radiocsirt.org/vuln/fkie_cve-2026-35563 <p>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.</p> <p>The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.</p> <p>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&#39;s configured trust store.</p> <p>The hostname verification has been enforced in the new version of the LDAP API</p> <p>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.</p> <p>The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.</p> <p>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&#39;s configured trust store.</p> <p>The hostname verification has been enforced in the new version of the LDAP API</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-35563 https://cve.radiocsirt.org/vuln/ghsa-85rw-g4f4-jprr <p><strong>Affected:</strong> Maven: org.apache.directory.api:api-ldap-client-api</p> <p>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.</p> <p>The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.</p> <p>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&#39;s configured trust store.</p> <p>The hostname verification has been enforced in the new version of the LDAP API.</p> <p><strong>Affected:</strong> Maven: org.apache.directory.api:api-ldap-client-api</p> <p>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.</p> <p>The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.</p> <p>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&#39;s configured trust store.</p> <p>The hostname verification has been enforced in the new version of the LDAP API.</p> https://cve.radiocsirt.org/vuln/ghsa-85rw-g4f4-jprr https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35563 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: apache-directory-api, Ubuntu:18.04:LTS: apache-directory-api, Ubuntu:20.04:LTS: apache-directory-api, Ubuntu:22.04:LTS: apache-directory-api, Ubuntu:24.04:LTS: apache-directory-api, Ubuntu:25.10: apache-directory-api, Ubuntu:26.04:LTS: apache-directory-api</p> <p>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&#39;s configured trust store. The hostname verification has been enforced in the new version of the LDAP API</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: apache-directory-api, Ubuntu:18.04:LTS: apache-directory-api, Ubuntu:20.04:LTS: apache-directory-api, Ubuntu:22.04:LTS: apache-directory-api, Ubuntu:24.04:LTS: apache-directory-api, Ubuntu:25.10: apache-directory-api, Ubuntu:26.04:LTS: apache-directory-api</p> <p>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&#39;s configured trust store. The hostname verification has been enforced in the new version of the LDAP API</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35563