<?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>Sun, 04 Oct 2026 20:52:31 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-13084</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-13084</link>
      <description>cnvd-2018-13084</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-13084</guid>
    </item>
    <item>
      <title>EUVD-2026-179539</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-179539</link>
      <description>EUVD-2026-179539</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-179539</guid>
    </item>
    <item>
      <title>fkie_cve-2018-1337</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-1337</link>
      <description>&lt;p&gt;In Apache Directory LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Apache Directory LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-1337</guid>
    </item>
    <item>
      <title>GHSA-cfw5-v7cw-69cw — Credential leak in org.apache.directory.api:apache-ldap-api</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cfw5-v7cw-69cw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.directory.api:apache-ldap-api&lt;/p&gt;
&lt;p&gt;In Apache LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.directory.api:apache-ldap-api&lt;/p&gt;
&lt;p&gt;In Apache LDAP API before 1.0.2, a bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS layer has been established, if the connection has already been used and put back in a pool of connections, leading to leaking any information contained in this request (including the credentials when sending a BIND request).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cfw5-v7cw-69cw</guid>
    </item>
    <item>
      <title>gsd-2018-1337</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-1337</link>
      <description>gsd-2018-1337</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-1337</guid>
    </item>
  </channel>
</rss>
