@auth/core
Affected
- introduced
0.1.0, fixed0.41.3(semver)
Fixed versions
0.41.3
Fix
- Fixed version
0.41.3npm install @auth/[email protected]
Advisory
Also known as: CVE-2026-73420
Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass
Summary
The default email-address normalizer used by the email/magic-link sign-in flow validates the address before applying Unicode normalization. An address can contain a Unicode character that is not an ASCII @ (U+0040) but canonicalizes to one under NFKC/NFKD normalization (the normalization commonly applied by mail libraries and services for internationalized email). Such an address passes the normalizer's single-@ check, but a downstream mail library that normalizes the string then sees two @ separators and may deliver the passwordless sign-in link to a different recipient than intended. This is an instance of validating before canonicalizing.
Am I affected?
You may be affected if all of the following hold:
next-auth >= 4.0.0, < 4.24.14, or @auth/core >= 0.1.0, < 0.41.3.normalizeIdentifier).sendVerificationRequest implementation uses a mail library or delivery service that applies Unicode normalization to recipient addresses (most internationalized-email/SMTPUTF8-capable senders do).You are not affected if you do not use the email provider, or if your normalizer/mailer rejects or canonicalizes non-ASCII addresses before they are validated.
Impact
Patched version
The fix applies Unicode (NFKC) normalization before the address is validated, so homoglyph separators are collapsed and rejected up front. Upgrade to the first release containing this fix (pending; this advisory will be updated with the exact patched version before publication). No application code changes are required after upgrading.
Workarounds
If you cannot upgrade immediately:
normalizeIdentifier on the email provider that calls identifier.normalize("NFKC") (and lower-cases/trims) before any validation, and rejects addresses that do not contain exactly one @ after normalization.Credit
Reported by @kakashi-kx. Thank you for the responsible disclosure.
Critical Basis: The source's own band: CRITICAL
0.1.0, fixed 0.41.3 (semver)0.41.3
0.41.3npm install @auth/[email protected]4.10.3, fixed 4.24.15 (semver)4.24.15
4.24.15npm install [email protected]5.0.0-beta.1, fixed 5.0.0-beta.32 (semver)5.0.0-beta.32
5.0.0-beta.32npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0