Account takeover via pre-normalization email validation
Published Aug 13, 2026 · Updated Aug 13, 2026
Email normalization in affected Auth.js packages allows remote attackers to take over accounts via misrouted passwordless sign-in links. The defaultNormalizer checks for a single ASCII at-sign before NFKC normalization, allowing a homoglyph to become a second separator during downstream mail handling. Affected releases require the email provider, built-in normalizer, and a sender that normalizes Unicode; no victim interaction is required.
Summary
What happened
Email normalization in affected Auth.js packages allows remote attackers to take over accounts via misrouted passwordless sign-in links. The defaultNormalizer checks for a single ASCII at-sign before NFKC normalization, allowing a homoglyph to become a second separator during downstream mail handling. Affected releases require the email provider, built-in normalizer, and a sender that normalizes Unicode; no victim interaction is required.
The record
- CVE
- CVE-2026-73420
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Auth.js
- Product
- @auth/core
- Classifications
- CWE-180, T1078
- 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=>= 0.1.0, < 0.41.3
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