<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T08:38:26.596258+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2020-15240</id>
    <title>CVE-2020-15240 — Regression in JWT Signature Validation</title>
    <updated>2026-10-12T08:38:26.597751+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> auth0 omniauth-auth0</p>
<p>omniauth-auth0 (rubygems) versions &gt;= 2.3.0 and &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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-15240"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-58r4-h6v8-jcvm</id>
    <title>GHSA-58r4-h6v8-jcvm — Regression in JWT Signature Validation</title>
    <updated>2026-10-12T08:38:26.597801+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: omniauth-auth0</p>
<p>### 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.</p>
<p>### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:</p>
<p>- 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.</p>
<p>### How to fix that?
Upgrade to version `2.4.1`.</p>
<p>### Will this update impact my users?
The fix provided in this version will not affect your users.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-58r4-h6v8-jcvm"/>
  </entry>
</feed>
