Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
HIGH severity

GHSA-58r4-h6v8-jcvm

HIGHFix: auth0/omniauth-auth0@fd3a14f

GHSA-58r4-h6v8-jcvm is a high-severity (CVSS 7.4) Improper Authentication vulnerability in omniauth-auth0. O3 Security confirms whether GHSA-58r4-h6v8-jcvm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Regression in JWT Signature Validation

Also known asCVE-2020-15240
Published
Nov 3, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
💎omniauth-auth0

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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.

Am I affected?

You are affected by this vulnerability if all of the following conditions apply:

  • 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.

How to fix that?

Upgrade to version 2.4.1.

Will this update impact my users?

The fix provided in this version will not affect your users.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsomniauth-auth02.3.0&&< 2.4.12.4.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for omniauth-auth0. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update omniauth-auth0 to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58r4-h6v8-jcvm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-58r4-h6v8-jcvm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-58r4-h6v8-jcvm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Am I affected? You are affected by this vulnerability if all of the following conditions apply: - 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. ### How to fix that?
O3 Security · Impact-Aware SCA

Is GHSA-58r4-h6v8-jcvm in your dependencies?

O3 detects GHSA-58r4-h6v8-jcvm across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.