Skip to main content
CVE-2025-67490VulnerabilityPublished

CVE-2025-67490: nextjs-auth0 · Incorrect Authorization

Affects nextjs-auth0Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium · fixed in 4.11.2 : update nextjs-auth0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.11.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

The primary mitigation is to upgrade the Auth0 Next.js SDK to versions 4.11.2 or 4.12.1 or later, where the concurrency issue in TokenRequestCache is resolved. Organizations should audit their applications to identify usage of affected versions and enforce upgrade policies. Additionally, developers should review token caching and session management logic to ensure thread-safe and request-isolated handling of authentication tokens. Implementing strict session validation and monitoring for anomalous token usage can help detect exploitation attempts. Where immediate upgrades are not feasible, applying application-level concurrency controls to serialize token requests or isolate user sessions can reduce risk. Security teams should also review logs for unusual authentication patterns and prepare incident response plans for potential token leakage. Finally, educating developers on secure token management practices in asynchronous environments is recommended to prevent similar issues.

Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

References

Community reviews

Loading reviews…