<?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>Sat, 03 Oct 2026 21:10:53 +0000</lastBuildDate>
    <item>
      <title>BIT-nats-2026-33248 — NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching</title>
      <link>https://cve.radiocsirt.org/vuln/bit-nats-2026-33248</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: nats&lt;/p&gt;
&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: nats&lt;/p&gt;
&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-nats-2026-33248</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-YK24413 — Security fix for CVE-2026-33248 applied in: nats-server-fips 2.12.5-r1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-yk24413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: nats-server-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the nats-server-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: nats-server-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the nats-server-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-yk24413</guid>
    </item>
    <item>
      <title>EUVD-2026-277686</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277686</link>
      <description>EUVD-2026-277686</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277686</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33248</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33248</link>
      <description>&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33248</guid>
    </item>
    <item>
      <title>GHSA-3f24-pcvm-5jqc — NATS has mTLS verify_and_map authentication bypass via incorrect Subject DN matching</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3f24-pcvm-5jqc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nats-io/nats-server/v2, Go: github.com/nats-io/nats-server&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.&lt;/p&gt;
&lt;p&gt;One authentication model supported is mTLS, deriving the NATS client identity from properties of the TLS Client Certificate.&lt;/p&gt;
&lt;p&gt;### Problem Description&lt;/p&gt;
&lt;p&gt;When using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass.&lt;/p&gt;
&lt;p&gt;This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely.&lt;/p&gt;
&lt;p&gt;So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Fixed in nats-server 2.12.6 &amp;amp; 2.11.15&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Developers should review their CA issuing practices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nats-io/nats-server/v2, Go: github.com/nats-io/nats-server&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.&lt;/p&gt;
&lt;p&gt;One authentication model supported is mTLS, deriving the NATS client identity from properties of the TLS Client Certificate.&lt;/p&gt;
&lt;p&gt;### Problem Description&lt;/p&gt;
&lt;p&gt;When using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass.&lt;/p&gt;
&lt;p&gt;This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely.&lt;/p&gt;
&lt;p&gt;So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Fixed in nats-server 2.12.6 &amp;amp; 2.11.15&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Developers should review their CA issuing practices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3f24-pcvm-5jqc</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-33248</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33248</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: nats-server, Ubuntu:25.10: nats-server, Ubuntu:Pro:26.04:LTS: nats-server&lt;/p&gt;
&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: nats-server, Ubuntu:25.10: nats-server, Ubuntu:Pro:26.04:LTS: nats-server&lt;/p&gt;
&lt;p&gt;NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.15 and 2.12.6, when using mTLS for client identity, with `verify_and_map` to derive a NATS identity from the client certificate&amp;#39;s Subject DN, certain patterns of RDN would not be correctly enforced, allowing for authentication bypass. This does require a valid certificate from a CA already trusted for client certificates, and `DN` naming patterns which the NATS maintainers consider highly unlikely. So this is an unlikely attack. Nonetheless, administrators who have been very sophisticated in their `DN` construction patterns might conceivably be impacted. Versions 2.11.15 and 2.12.6 contain a fix. As a workaround, developers should review their CA issuing practices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33248</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0858 — NATS Server: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0858</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in NATS Server ausnutzen, um Informationen offenzulegen oder zu manipulieren, einen Denial-of-Service zu verursachen und Sicherheitsmechanismen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in NATS Server ausnutzen, um Informationen offenzulegen oder zu manipulieren, einen Denial-of-Service zu verursachen und Sicherheitsmechanismen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0858</guid>
    </item>
  </channel>
</rss>
