Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-73421

Auth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error)

Overview

Published
13 Aug 2026
Modified
18 Sep 2026
Critical CVE
1 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available
CVSS score Critical, no score

Description

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.

Source: OX vulnerability database

Severity

CRITICAL

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-285, CWE-636

Affected packages · 1

Packages affected by CVE-2026-73421
EcosystemPackageVulnerableFixed in
npm next-auth >=5.0.0-beta.0, <5.0.0-beta.32 5.0.0-beta.32

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.