CVE-2026-40155 affects the Auth0 Next.js SDK in versions 4.12.0 through 4.17.1. The vulnerability is a race condition in handling simultaneous requests that trigger a nonce retry, causing the proxy cache fetcher to perform improper lookups for token request results. In affected deployments, this can result in token request results or related cached proxy responses being associated with the wrong concurrent user. The issue is specifically described as affecting projects that use the proxy handler paths /me/* and /my-org/* with DPoP enabled. Under those conditions, sensitive data such as session identifiers, access tokens, or API response payloads belonging to one user may be routed to another concurrent user. The issue was fixed in version 4.18.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.