<?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>Mon, 12 Oct 2026 07:35:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-42759</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-42759</link>
      <description>EUVD-2026-42759</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-42759</guid>
    </item>
    <item>
      <title>fkie_cve-2020-15240</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-15240</link>
      <description>&lt;p&gt;omniauth-auth0 (rubygems) versions &amp;gt;= 2.3.0 and &amp;lt; 2.4.1 improperly validate the JWT token signature when using the `jwt_validator.verify` method. Improper validation of the JWT token signature can allow an attacker to bypass authentication and authorization. You are affected by this vulnerability if all of the following conditions apply: 1. You are using `omniauth-auth0`. 2. You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow. The issue is patched in version 2.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;omniauth-auth0 (rubygems) versions &amp;gt;= 2.3.0 and &amp;lt; 2.4.1 improperly validate the JWT token signature when using the `jwt_validator.verify` method. Improper validation of the JWT token signature can allow an attacker to bypass authentication and authorization. You are affected by this vulnerability if all of the following conditions apply: 1. You are using `omniauth-auth0`. 2. You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow. The issue is patched in version 2.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-15240</guid>
    </item>
    <item>
      <title>GHSA-58r4-h6v8-jcvm — Regression in JWT Signature Validation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-58r4-h6v8-jcvm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: omniauth-auth0&lt;/p&gt;
&lt;p&gt;### Overview
Versions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method.  Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.&lt;/p&gt;
&lt;p&gt;### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:&lt;/p&gt;
&lt;p&gt;- You are using `omniauth-auth0`.
- You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow.&lt;/p&gt;
&lt;p&gt;### How to fix that?
Upgrade to version `2.4.1`.&lt;/p&gt;
&lt;p&gt;### Will this update impact my users?
The fix provided in this version will not affect your users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: omniauth-auth0&lt;/p&gt;
&lt;p&gt;### Overview
Versions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method.  Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.&lt;/p&gt;
&lt;p&gt;### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:&lt;/p&gt;
&lt;p&gt;- You are using `omniauth-auth0`.
- You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow.&lt;/p&gt;
&lt;p&gt;### How to fix that?
Upgrade to version `2.4.1`.&lt;/p&gt;
&lt;p&gt;### Will this update impact my users?
The fix provided in this version will not affect your users.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-58r4-h6v8-jcvm</guid>
    </item>
    <item>
      <title>gsd-2020-15240</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-15240</link>
      <description>gsd-2020-15240</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-15240</guid>
    </item>
  </channel>
</rss>
