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

> Attackers can retrieve cached authentication tokens across user sessions in SSR environments due to improper cache isolation in the Auth0 React Native SDK.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026

## What is CVE-2026-84685?

CVE-2026-84685 is a medium-severity vulnerability in react-native-auth0, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-488 (Exposure of Data Element to Wrong Session)

## Which versions are affected by CVE-2026-84685?


## How do I fix CVE-2026-84685?

No fix has been published for CVE-2026-84685 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84685 being exploited?

There is no known exploitation of CVE-2026-84685 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84685 and fix it if it is affected.

What it is: CVE-2026-84685 is a medium-severity vulnerability in react-native-auth0, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84685 in the wild and no public exploit code.

Affected product: react-native-auth0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84685/ (Markdown: https://insights.sbomify.com/CVE-2026-84685/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84685
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84685
- OSV: https://osv.dev/vulnerability/CVE-2026-84685

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84685/
Summaries are generated and may contain mistakes; the official description above is the record.