Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.0%top 93%

CVE-2026-40155: CWE-863: Incorrect Authorization in auth0 nextjs-auth0

0
Medium
VulnerabilityCVE-2026-40155cvecve-2026-40155cwe-863cwe-362
Published: Fri Apr 17 2026 (04/17/2026, 20:54:38 UTC)
Source: CVE Database V5
Vendor/Project: auth0
Product: nextjs-auth0

Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. In versions 4.12.0 through 4.17.1, simultaneous requests that trigger a nonce retry may cause the proxy cache fetcher to perform improper lookups for the token request results. Users are affected if their project uses both the vulnerable versions and the proxy handler /me/* and /my-org/* with DPoP enabled. This issue has been fixed in version 4.18.0.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/25/2026, 02:55:46 UTC

Technical Analysis

The Auth0 Next.js SDK versions 4.12.0 to 4.17.1 contain an incorrect authorization flaw (CWE-863) related to handling simultaneous requests that trigger nonce retries. This leads the proxy cache fetcher to perform improper lookups for token request results, potentially exposing token data or allowing unauthorized access. The issue specifically impacts projects using the proxy handler endpoints /me/* and /my-org/* with DPoP enabled. The vulnerability was addressed and fixed in version 4.18.0 of the SDK.

Potential Impact

If exploited, this vulnerability could lead to improper authorization checks resulting in exposure of token information or unauthorized access to user data. The impact is limited to applications using the specified vulnerable versions with the proxy handlers /me/* and /my-org/* and DPoP enabled. There are no known exploits in the wild at this time.

Mitigation Recommendations

Upgrade to Auth0 Next.js SDK version 4.18.0 or later, where this issue has been fixed. Since this is a library vulnerability, applying the official update is the recommended remediation. No other mitigations are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-09T19:31:56.013Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69e2a136bdfbbecc59908353

Added to database: 4/17/2026, 9:08:06 PM

Last enriched: 4/25/2026, 2:55:46 AM

Last updated: 6/2/2026, 12:42:49 PM

Views: 69

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses