Is CVE-2025-67490 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-67490 being exploited in the wild.

How severe is CVE-2025-67490?

Medium severity, with a CVSS score of 5.4, published 10 December 2025.

Which products and versions are affected?

@auth0/nextjs-auth0 (npm) SEMVER:introduced=4.11.0,fixed=4.11.2.

Is there a fix for CVE-2025-67490?

Yes. @auth0/nextjs-auth0 (npm): upgrade to 4.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-67490 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-67490?

Check whether you run @auth0/nextjs-auth0 (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-67490: Auth0 Next.js SDK improper request caching lookup

CVE-2025-67490 · Severity: medium · CVSS 5.4 · Published 2025-12-10

The Auth0 Next.js SDK is a library that developers use to add authentication and user management to web applications. When multiple user requests are processed simultaneously by the same SDK instance, the library may incorrectly cache and retrieve token data, potentially allowing one user's authentication tokens to be returned to another user. This could enable an attacker to impersonate other users and access their accounts or sensitive data.

Technologies: @auth0/nextjs-auth0 (npm). Vendors: npm.

Quick answers

Is CVE-2025-67490 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-67490 being exploited in the wild.
How severe is CVE-2025-67490?: Medium severity, with a CVSS score of 5.4, published 10 December 2025.
Which products and versions are affected?: @auth0/nextjs-auth0 (npm) SEMVER:introduced=4.11.0,fixed=4.11.2.
Is there a fix for CVE-2025-67490?: Yes. @auth0/nextjs-auth0 (npm): upgrade to 4.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-67490 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-67490?: Check whether you run @auth0/nextjs-auth0 (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@auth0/nextjs-auth0 (npm): upgrade to 4.11.2 or later
```
npm install @auth0/nextjs-auth0@4.11.2
```

Technical details

The vulnerability is an improper authorization/cache lookup issue (CWE-863) in the TokenRequestCache component of the Auth0 Next.js SDK. When handling concurrent requests with a singleton SDK instance, the cache lookup fails to properly differentiate between simultaneous requests, resulting in cross-request token leakage. The attack requires network access and low-level privileges, but user interaction and specific timing conditions are needed. An attacker can extract authentication tokens belonging to other concurrent users, potentially achieving account takeover or unauthorized access to protected resources. The vulnerability affects versions 4.11.0, 4.11.1, and 4.12.0; patches are available in versions 4.11.2 and 4.12.1.

Affected products

Auth0 Next.js SDK 4.11.0, 4.11.1, 4.12.0

Identifiers

CVE-2025-67490
GHSA-wcgj-f865-c7j7

Timeline

2025-12-10: disclosed
2025-12-10: patched: Fixed in versions 4.11.2 and 4.12.1

References

https://github.com/auth0/nextjs-auth0/security/advisories/GHSA-wcgj-f865-c7j7

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.