CVE-2026-40155Network attack vector

Cross-session token exposure via cached proxy fetcher

Published Apr 17, 2026 · Updated Apr 17, 2026

Incorrect authorization in Auth0 Next.js SDK 4.12.0 through 4.17.1 allows remote authenticated users to receive a different session's token. The proxy handler caches a request-bound Fetcher by domain and audience, then mutates its token callback, allowing concurrent nonce retries to resolve against a different session. Exploitation requires concurrent profile or organization proxy requests with DPoP enabled and user interaction; the mismatched token exposes protected account data and enables limited unauthorized changes.

CVSS severity5.4
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in Auth0 Next.js SDK 4.12.0 through 4.17.1 allows remote authenticated users to receive a different session's token. The proxy handler caches a request-bound Fetcher by domain and audience, then mutates its token callback, allowing concurrent nonce retries to resolve against a different session. Exploitation requires concurrent profile or organization proxy requests with DPoP enabled and user interaction; the mismatched token exposes protected account data and enables limited unauthorized changes.

The record

CVE
CVE-2026-40155
Published
Apr 17, 2026
Updated
Apr 17, 2026
Vendor
Auth0
Product
Auth0 Next.js SDK
Classifications
CWE-863, CWE-362, T1528
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 17, 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.

  1. Affected versionversion=>= 4.12.0, < 4.18.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Auth0 · Auth0 Next.js SDKversion=>= 4.12.0, < 4.18.0

Published CVSS scores

5.4GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1528Steal Application Access Token

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