CVE-2026-40155 | auth0 nextjs-auth0 up to 4.17.x authorization (GHSA-xq8m-7c5p-c2r6)

VDB-358128 · CVE-2026-40155 · GHSA-XQ8M-7C5P-C2R6 AUTH0 NEXTJS-AUTH0 UP TO 4.17.X AUTHORIZATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 2.09+ Summaryinfo A vulnerability categorized as problematic has been discovered in auth0 nextjs-auth0 up to 4.17.x. Affected by this issue is some unknown functionality. The manipulation results in authorization. This vulnerability was named CVE-2026-40155. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component. Detailsinfo A vulnerability classified as problematic has been found in auth0 nextjs-auth0 up to 4.17.x. Affected is an unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: 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. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-40155 since 04/09/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available. Upgrading to version 4.18.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 98c36dc306970c2230ea1a32efef431d29b99978 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor auth0 Name nextjs-auth0 Version 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 License open-source Website Product: https://github.com/auth0/nextjs-auth0/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.2 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.0 VulDB Temp Score: 4.8 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.4 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Authorization CWE: CWE-863 / CWE-285 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: nextjs-auth0 4.18.0 Patch: 98c36dc306970c2230ea1a32efef431d29b99978 Timelineinfo 04/09/2026 CVE reserved 04/17/2026 +8 days Advisory disclosed 04/17/2026 +0 days VulDB entry created 04/17/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-xq8m-7c5p-c2r6 Status: Confirmed CVE: CVE-2026-40155 (🔒) GCVE (CVE): GCVE-0-2026-40155 GCVE (VulDB): GCVE-100-358128 Entryinfo Created: 04/17/2026 23:51 Changes: 04/17/2026 23:51 (66) Complete: 🔍 Cache ID: 99:B8B:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸