CVE-2026-73420

CVE-2026-73420 · NextAuth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

NextAuth.js provides authentication for Next.js. Prior to @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32, the defaultNormalizer used by the email and magic-link sign-in flow validates an address before applying Unicode normalization. An address can contain a Unicode character such as U+FF20 FULLWIDTH COMMERCIAL AT that is not ASCII at-sign but canonicalizes to an ASCII at-sign under NFKC or NFKD normalization. The address passes the normalizer's single-at-sign check, but a downstream sendVerificationRequest mail library or delivery service that normalizes the address can then see two at-sign separators and deliver the passwordless sign-in link to an attacker-controlled recipient. Applications are affected when the email provider uses the built-in normalizer rather than a custom normalizeIdentifier and the downstream sender applies Unicode normalization. An attacker who knows a victim's email address can request the misrouted magic link and sign in as the victim without victim interaction. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32.

CVSS 9.1 · Critique · EPSS 0,7% · Correctif disponible

Publication

2026-08-13T22:04:15.414Z

Mise à jour

2026-08-14T15:06:00.594Z

Pile logicielle: node

Vérifiez votre serveur →