<?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>Wed, 07 Oct 2026 21:00:54 +0000</lastBuildDate>
    <item>
      <title>BIT-nats-2021-3127</title>
      <link>https://cve.radiocsirt.org/vuln/bit-nats-2021-3127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: nats&lt;/p&gt;
&lt;p&gt;NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&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 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-nats-2021-3127</guid>
    </item>
    <item>
      <title>cnvd-2021-26378</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-26378</link>
      <description>cnvd-2021-26378</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-26378</guid>
    </item>
    <item>
      <title>EUVD-2026-20699</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-20699</link>
      <description>EUVD-2026-20699</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-20699</guid>
    </item>
    <item>
      <title>fkie_cve-2021-3127</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-3127</link>
      <description>&lt;p&gt;NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-3127</guid>
    </item>
    <item>
      <title>GHSA-62mh-w5cv-p88c — nats-io/jwt not enforcing checking of Import token permissions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-62mh-w5cv-p88c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nats-io/jwt, Go: github.com/nats-io/jwt/v2&lt;/p&gt;
&lt;p&gt;(This advisory is canonically &amp;lt;https://advisories.nats.io/CVE/CVE-2021-3127.txt&amp;gt;)&lt;/p&gt;
&lt;p&gt;## Problem Description&lt;/p&gt;
&lt;p&gt;The NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects.  Some Exports are public, such that anyone can import the
relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.&lt;/p&gt;
&lt;p&gt;The JWT library&amp;#39;s validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.&lt;/p&gt;
&lt;p&gt;As a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the
importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.&lt;/p&gt;
&lt;p&gt;The NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.&lt;/p&gt;
&lt;p&gt;The CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;#### JWT library&lt;/p&gt;
&lt;p&gt;* all versions prior to 2.0.1
 * fixed after nats-io/jwt#149 landed (2021-03-14)&lt;/p&gt;
&lt;p&gt;#### NATS Server&lt;/p&gt;
&lt;p&gt;* Version 2 prior to 2.2.0
   + 2.0.0 through and including 2.1.9 are vulne…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nats-io/jwt, Go: github.com/nats-io/jwt/v2&lt;/p&gt;
&lt;p&gt;(This advisory is canonically &amp;lt;https://advisories.nats.io/CVE/CVE-2021-3127.txt&amp;gt;)&lt;/p&gt;
&lt;p&gt;## Problem Description&lt;/p&gt;
&lt;p&gt;The NATS server provides for Subjects which are namespaced by Account; all Subjects are supposed to be private to an account, with an Export/Import system used to grant cross-account access to some Subjects.  Some Exports are public, such that anyone can import the
relevant subjects, and some Exports are private, such that the Import requires a token JWT to prove permission.&lt;/p&gt;
&lt;p&gt;The JWT library&amp;#39;s validation of the bindings in the Import Token incorrectly warned on mismatches, instead of outright rejecting the token.&lt;/p&gt;
&lt;p&gt;As a result, any account can take an Import token used by any other account and re-use it for themselves because the binding to the
importing account is not rejected, and use it to import *any* Subject from the Exporting account, not just the Subject referenced in the Import Token.&lt;/p&gt;
&lt;p&gt;The NATS account-server system treats account JWTs as semi-public information, such that an attacker can easily enumerate all account JWTs and retrieve all Import Tokens from those account JWTs.&lt;/p&gt;
&lt;p&gt;The CVE identifier should cover the JWT library repair and the nats-server containing the fixed JWT library, and any other application depending upon the fixed JWT library.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;#### JWT library&lt;/p&gt;
&lt;p&gt;* all versions prior to 2.0.1
 * fixed after nats-io/jwt#149 landed (2021-03-14)&lt;/p&gt;
&lt;p&gt;#### NATS Server&lt;/p&gt;
&lt;p&gt;* Version 2 prior to 2.2.0
   + 2.0.0 through and including 2.1.9 are vulne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-62mh-w5cv-p88c</guid>
    </item>
    <item>
      <title>gsd-2021-3127</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-3127</link>
      <description>gsd-2021-3127</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-3127</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-3127</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-github-nats-io-jwt, Ubuntu:22.04:LTS: golang-github-nats-io-jwt&lt;/p&gt;
&lt;p&gt;NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-github-nats-io-jwt, Ubuntu:22.04:LTS: golang-github-nats-io-jwt&lt;/p&gt;
&lt;p&gt;NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3127</guid>
    </item>
  </channel>
</rss>
