<?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>Fri, 09 Oct 2026 10:21:22 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-223267</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-223267</link>
      <description>EUVD-2026-223267</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-223267</guid>
    </item>
    <item>
      <title>fkie_cve-2022-27890</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-27890</link>
      <description>&lt;p&gt;It was discovered that the sls-logging was not verifying hostnames in TLS certificates due to a misuse of the javax.net.ssl.SSLSocketFactory API. A malicious attacker in a privileged network position could abuse this to perform a man-in-the-middle attack. A successful man-in-the-middle attack would allow them to intercept, read, or modify network communications to and from the affected service. In the case of AtlasDB, the vulnerability was mitigated by other network controls such as two-way TLS when deployed as part of a Palantir platform. Palantir still recommends upgrading to a non-vulnerable version out of an abundance of caution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;It was discovered that the sls-logging was not verifying hostnames in TLS certificates due to a misuse of the javax.net.ssl.SSLSocketFactory API. A malicious attacker in a privileged network position could abuse this to perform a man-in-the-middle attack. A successful man-in-the-middle attack would allow them to intercept, read, or modify network communications to and from the affected service. In the case of AtlasDB, the vulnerability was mitigated by other network controls such as two-way TLS when deployed as part of a Palantir platform. Palantir still recommends upgrading to a non-vulnerable version out of an abundance of caution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-27890</guid>
    </item>
    <item>
      <title>GHSA-v8rr-9cww-2334</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v8rr-9cww-2334</link>
      <description>&lt;p&gt;It was discovered that the sls-logging was not verifying hostnames in TLS certificates due to a misuse of the javax.net.ssl.SSLSocketFactory API. A malicious attacker in a privileged network position could abuse this to perform a man-in-the-middle attack. A successful man-in-the-middle attack would allow them to intercept, read, or modify network communications to and from the affected service. In the case of AtlasDB, the vulnerability was mitigated by other network controls such as two-way TLS when deployed as part of a Palantir platform. Palantir still recommends upgrading to a non-vulnerable version out of an abundance of caution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;It was discovered that the sls-logging was not verifying hostnames in TLS certificates due to a misuse of the javax.net.ssl.SSLSocketFactory API. A malicious attacker in a privileged network position could abuse this to perform a man-in-the-middle attack. A successful man-in-the-middle attack would allow them to intercept, read, or modify network communications to and from the affected service. In the case of AtlasDB, the vulnerability was mitigated by other network controls such as two-way TLS when deployed as part of a Palantir platform. Palantir still recommends upgrading to a non-vulnerable version out of an abundance of caution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v8rr-9cww-2334</guid>
    </item>
    <item>
      <title>gsd-2022-27890</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-27890</link>
      <description>gsd-2022-27890</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-27890</guid>
    </item>
  </channel>
</rss>
