Is CVE-2026-84685 exploited in the wild?

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

How severe is CVE-2026-84685?

Medium severity, with a CVSS score of 6.5, published 8 September 2026.

Which products and versions are affected?

Auth0 React-Native-Auth0 5.0.0 through 5.11.0.

Is there a fix for CVE-2026-84685?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-84685 attacked?

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

Am I affected by CVE-2026-84685?

Check whether you run Auth0 React-Native-Auth0 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-2026-84685: Auth0 react-native-auth0 improper cache isolation in web platform

CVE-2026-84685 · Severity: medium · CVSS 6.5 · Published 2026-09-08

The react-native-auth0 SDK's web implementation does not properly isolate authentication tokens when used in server-side rendering environments where a single Node.js process handles requests from multiple users. An attacker could retrieve authentication tokens from other users' sessions cached in the server's memory, potentially gaining unauthorized access to their accounts and data.

Vendors: Auth0.

Quick answers

Is CVE-2026-84685 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-84685 being exploited in the wild.
How severe is CVE-2026-84685?: Medium severity, with a CVSS score of 6.5, published 8 September 2026.
Which products and versions are affected?: Auth0 React-Native-Auth0 5.0.0 through 5.11.0.
Is there a fix for CVE-2026-84685?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-84685 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-84685?: Check whether you run Auth0 React-Native-Auth0 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.

Technical details

This is a cache isolation vulnerability (CWE-488) affecting the web platform implementation of the react-native-auth0 SDK. The SDK maintains an in-memory token cache that is not scoped to individual user sessions; when multiple users authenticate through the same Node.js SSR server process, their tokens persist in shared module state across HTTP requests. The vulnerability is triggered when the SDK is explicitly configured with useDPoP: false (disabling Demonstration of Proof-of-Possession protection). An attacker with network access to the web application can retrieve tokens cached from other users' sessions, leading to cross-session credential exposure. The vulnerability affects versions 5.0.0 through 5.11.0; a patch is available in version 5.11.1 and later.

Affected products

Auth0 react-native-auth0 5.0.0 through 5.11.0

Timeline

2026-09-08: disclosed

References

https://trust.okta.com/security-advisories/improper-cache-isolation-in-auth0-react-native-auth0-sdk-web-platform-credential-management-cve-2026-84685

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