Cross-session token exposure via shared SSR cache
Published Sep 8, 2026 · Updated Sep 10, 2026
Cross-session data exposure in Auth0 react-native-auth0 5.0.0 through 5.11.0 allows remote attackers to retrieve cached tokens. The web credential manager stores tokens in module-level memory without scoping the cache to a user session, so a later request can receive another user's token. Exposure requires a persistent Node.js SSR process, useDPoP:false instead of the enabled default, and multiple users authenticating through that process.
Summary
What happened
Cross-session data exposure in Auth0 react-native-auth0 5.0.0 through 5.11.0 allows remote attackers to retrieve cached tokens. The web credential manager stores tokens in module-level memory without scoping the cache to a user session, so a later request can receive another user's token. Exposure requires a persistent Node.js SSR process, useDPoP:false instead of the enabled default, and multiple users authenticating through that process.
The record
- CVE
- CVE-2026-84685
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Auth0
- Product
- react-native-auth0
- Classifications
- CWE-488, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <5.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo