https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T20:46:44.421606+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cleanstart-2026-eu32419 CLEANSTART-2026-EU32419 — It was identified that the LDAP client implementation in version 2 2026-10-04T20:46:44.427002+00:00

Affected: CleanStart: keycloak

Security vulnerability affects the keycloak package. It was identified that the LDAP client implementation in version 2.

 https://cve.radiocsirt.org/vuln/euvd-2026-323317 EUVD-2026-323317 2026-10-04T20:46:44.427071+00:00 EUVD-2026-323317 https://cve.radiocsirt.org/vuln/fkie_cve-2026-35563 fkie_cve-2026-35563 2026-10-04T20:46:44.427088+00:00

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

 https://cve.radiocsirt.org/vuln/ghsa-85rw-g4f4-jprr GHSA-85rw-g4f4-jprr — Apache Directory LDAP API lacks server certificate verification for LDAP hostnames 2026-10-04T20:46:44.427122+00:00

Affected: Maven: org.apache.directory.api:api-ldap-client-api

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.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35563 UBUNTU-CVE-2026-35563 2026-10-04T20:46:44.427149+00:00

Affected: 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

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