<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 06:39:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-35563 — Apache Directory LDAP API: LDAP client implementation does not verify if the server certificate matches the intended LD…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-35563</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Directory LDAP API&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The
 root cause of this vulnerability lies in the incomplete TLS server 
identity verification within the LDAP client implementation.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s configured trust store.&lt;/p&gt;
&lt;p&gt;The hostname verification has been enforced in the new version of the LDAP API&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Directory LDAP API&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The
 root cause of this vulnerability lies in the incomplete TLS server 
identity verification within the LDAP client implementation.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s configured trust store.&lt;/p&gt;
&lt;p&gt;The hostname verification has been enforced in the new version of the LDAP API&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-35563</guid>
    </item>
  </channel>
</rss>
