Authentication bypass via truthy session error object
Published Aug 13, 2026 · Updated Aug 13, 2026
Improper authorization in NextAuth.js 5.0.0-beta.0 through 5.0.0-beta.31 allows remote attackers to access protected routes. The auth() wrapper parses a non-OK session response into a truthy error object rather than null, so bare auth-object existence checks pass. Exploitation requires a server configuration error and an application that treats auth-object existence alone as authentication; valid configurations are unaffected.
Summary
What happened
Improper authorization in NextAuth.js 5.0.0-beta.0 through 5.0.0-beta.31 allows remote attackers to access protected routes. The auth() wrapper parses a non-OK session response into a truthy error object rather than null, so bare auth-object existence checks pass. Exploitation requires a server configuration error and an application that treats auth-object existence alone as authentication; valid configurations are unaffected.
The record
- CVE
- CVE-2026-73421
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Auth.js
- Product
- NextAuth.js
- Classifications
- CWE-285, CWE-636, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 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.
- Affected versionversion=>= 5.0.0-beta.4, < 5.0.0-beta.32
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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