Auth bypass in Nextauthjs Next-Auth

CVE-2026-73421

NextAuth.js provides authentication for Next.js. From next-auth 5.0.0-beta.0 until 5.0.0-beta.32, applications that gate access by checking only for the existence of the auth object returned by the auth() wrapper can fail open when Auth.js has a server configuration error. In middleware, Route Handlers, React Server Components, and other auth() entry points, a non-OK session response is parsed into a truthy error object instead of null, so checks such as !!auth and if (req.auth) evaluate to true for unauthenticated requests. A provider missing both the issuer and authorization endpoint triggers InvalidEndpoints, and an unset AUTH_SECRET or another server configuration error can produce the same behavior. There is no impact while configuration is valid, but after a deployment becomes misconfigured, routes protected only by session existence silently grant access to every visitor. This issue is fixed in next-auth 5.0.0-beta.32.

Published · last modified .

EPSS exploit prediction

EPSS: 0.006 (48.8th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 49th percentile — 48.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-73421: held from 0.005 to 0.006.

EPSS over last 30 days · oldest: 0.005 · newest: 0.006 · change: +0.002

Affected products

Weakness classification (CWE)

References