CVE-2026-73420: nextauthjs next-auth · Incorrect Behavior Order: Validate Before Canonicalize
Affects nextauthjs next-authSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 5.0.0-beta.32 or 4.24.15 as a priority.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.0-beta.32, 4.24.15, 0.41.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade next-auth to 5.0.0-beta.32 or 4.24.15; core to 0.41.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nextauthjsnext-auth | Affected
| Fixed in
|
| nextauthjsnext-auth | Affected
| Fixed in
|
| @authcore | Affected
| Fixed in
|
AI-suggested
A fix is available in @auth/core 0.41.3, next-auth 4.24.15, and 5.0.0-beta.32. Users should upgrade to these or later versions to resolve the issue. Applications using a custom normalizeIdentifier or not relying on the built-in normalizer may not be affected. Patch status is not explicitly stated beyond these fixed versions; verify with vendor advisories for the latest remediation guidance.
Description
CVE-2026-73420 is a critical vulnerability in NextAuth.js affecting the email and magic-link sign-in flow. The default email address normalizer validates the address before applying Unicode normalization, allowing an attacker to exploit Unicode characters that canonicalize to ASCII at-signs. This can cause a misrouting of passwordless sign-in links to attacker-controlled addresses, enabling unauthorized sign-in without victim interaction. The issue is fixed in @auth/core 0.41.3, next-auth 4.24.15, and 5.0.0-beta.32.
References
- github.com/nextauthjs/next-auth/security/advisories/GHSA-7rqj-j65f-68wh (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/19d2feb24359fa8c79418907fc68d9ec8152ca94 (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/a63eee12a1a20cb35209e44195b097868517b9a0 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32 (opens in a new tab)