<?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>Tue, 06 Oct 2026 11:10:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-23540 — jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-23540</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; auth0 node-jsonwebtoken&lt;/p&gt;
&lt;p&gt;In versions `&amp;lt;=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the `none` algorithm. If you need &amp;#39;none&amp;#39; algorithm, you have to explicitly specify that in `jwt.verify()` options.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; auth0 node-jsonwebtoken&lt;/p&gt;
&lt;p&gt;In versions `&amp;lt;=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the `none` algorithm. If you need &amp;#39;none&amp;#39; algorithm, you have to explicitly specify that in `jwt.verify()` options.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-23540</guid>
    </item>
  </channel>
</rss>
