{"id":"GHSA-7rqj-j65f-68wh","revision":null,"records":[{"revision":"3e68699d7d6847e1a2d2daca6a5dbe1c","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-73420","aliases":[],"title":"NextAuth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass","description":"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.","state":0,"publishedAt":"2026-08-13T22:04:15.414+00:00","modifiedAt":"2026-08-14T15:06:00.594+00:00","affected":[{"ecosystem":"Vendor product","name":"next-auth","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"nextauthjs\",\n                    \"product\": \"next-auth\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 4.24.15\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 5.0.0-beta.4, < 5.0.0-beta.32\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"},{"ecosystem":"Vendor product","name":"core","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"@auth\",\n                    \"product\": \"core\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 0.1.0, < 0.41.3\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","score":9.1,"severity":"CRITICAL"}],"references":["https://github.com/nextauthjs/next-auth/security/advisories/GHSA-7rqj-j65f-68wh","https://github.com/nextauthjs/next-auth/commit/19d2feb24359fa8c79418907fc68d9ec8152ca94","https://github.com/nextauthjs/next-auth/commit/a63eee12a1a20cb35209e44195b097868517b9a0","https://github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-73420","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-73420","identifiers":["CVE-2026-73420"]},"retained":false,"historicalAffected":[]},{"revision":"768578efe4cb4116a71dd007d4e090d7","observedAt":"2026-11-11T16:05:18.275+00:00","statement":{"source":"euvd","id":"EUVD-2026-58519","aliases":["CVE-2026-73420","GHSA-7rqj-j65f-68wh"],"title":"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 normalizat…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","score":9.1,"severity":null}],"references":["https://github.com/nextauthjs/next-auth/security/advisories/GHSA-7rqj-j65f-68wh","https://github.com/nextauthjs/next-auth/commit/19d2feb24359fa8c79418907fc68d9ec8152ca94","https://github.com/nextauthjs/next-auth/commit/a63eee12a1a20cb35209e44195b097868517b9a0","https://github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-58519","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Aug 13, 2026, 10:04:15 PM","dateUpdated":"Aug 14, 2026, 3:06:00 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-58519","identifiers":["EUVD-2026-58519","CVE-2026-73420","GHSA-7rqj-j65f-68wh"]},"retained":false,"historicalAffected":[]},{"revision":"36d3b28f0d754848951251b970937ab8","observedAt":"2026-10-25T15:19:09.409+00:00","statement":{"source":"nvd","id":"CVE-2026-73420","aliases":[],"title":"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 normalizat…","description":"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.","state":0,"publishedAt":"2026-08-13T22:17:26.297+00:00","modifiedAt":"2026-09-18T20:05:53.723+00:00","affected":[],"metrics":[{"system":"CVSS 4.0 · security-advisories@github.com · Secondary","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","score":9.1,"severity":"CRITICAL"}],"references":["https://github.com/nextauthjs/next-auth/commit/19d2feb24359fa8c79418907fc68d9ec8152ca94","https://github.com/nextauthjs/next-auth/commit/a63eee12a1a20cb35209e44195b097868517b9a0","https://github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32","https://github.com/nextauthjs/next-auth/security/advisories/GHSA-7rqj-j65f-68wh"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-73420","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Awaiting Analysis","weaknesses":["CWE-180"],"productCriteria":[],"sourceDates":{"published":"2026-08-13T22:17:26.297","lastModified":"2026-09-18T20:05:53.723"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-73420","identifiers":["CVE-2026-73420"]},"retained":false,"historicalAffected":[]},{"revision":"d0b466e2dd044334b57c84579bc1a952","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-7rqj-j65f-68wh","aliases":["CVE-2026-73420"],"title":"Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass","description":"## Summary\n\nThe 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.\n\n## Am I affected?\n\nYou may be affected if **all** of the following hold:\n\n- You use `next-auth` `>= 4.0.0, < 4.24.14`, or `@auth/core` `>= 0.1.0, < 0.41.3`.\n- You have the email / magic-link (passwordless) provider enabled.\n- You rely on the built-in default identifier normalizer (you have not supplied your own `normalizeIdentifier`).\n- Your `sendVerificationRequest` implementation uses a mail library or delivery service that applies Unicode normalization to recipient addresses (most internationalized-email/SMTPUTF8-capable senders do).\n\nYou 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.\n\n## Impact\n\n- Account takeover: an attacker who knows a victim's email address can request a magic link that is delivered to an attacker-controlled mailbox, then use it to sign in as the victim.\n- No victim interaction is required to misroute the link; the attacker initiates the flow.\n\n## Patched version\n\nThe 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.\n\n## Workarounds\n\nIf you cannot upgrade immediately:\n\n- Supply a custom `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.\n- Or reject any address whose local part or domain contains non-ASCII characters, if your user base does not require internationalized email addresses.\n\n## Credit\n\nReported by @kakashi-kx. Thank you for the responsible disclosure.","state":0,"publishedAt":"2026-07-23T14:40:15+00:00","modifiedAt":"2026-09-10T03:50:51.5669451+00:00","affected":[{"ecosystem":"npm","name":"@auth/core","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.1.0"},{"kind":"fixed","version":"0.41.3"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"next-auth","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"4.10.3"},{"kind":"fixed","version":"4.24.15"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"next-auth","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"5.0.0-beta.1"},{"kind":"fixed","version":"5.0.0-beta.32"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"CRITICAL"}],"references":["https://github.com/nextauthjs/next-auth/security/advisories/GHSA-7rqj-j65f-68wh","https://github.com/nextauthjs/next-auth/commit/19d2feb24359fa8c79418907fc68d9ec8152ca94","https://github.com/nextauthjs/next-auth/commit/a63eee12a1a20cb35209e44195b097868517b9a0","https://github.com/nextauthjs/next-auth","https://github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15","https://github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32"],"sourceUrl":"https://github.com/advisories/GHSA-7rqj-j65f-68wh","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-7rqj-j65f-68wh","identifiers":["GHSA-7rqj-j65f-68wh","CVE-2026-73420"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-13T12:59:11.9732431+00:00","complete":true,"records":1779,"lastAttemptAt":"2026-11-13T12:59:11.9732431+00:00","lastSuccessAt":"2026-11-13T12:59:12.1229749+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:12.1229756+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-d8fa82e95fdb59244e2f635e667ba17f0796ca0a4f1f4bb8cc31febcd660b76c-f139040820e198a7b90c89ade0a85e4d1784f6cdedc33dd35667c553a90ed9b3","complete":true,"records":425359,"lastAttemptAt":"2026-11-13T12:57:12.1370926+00:00","lastSuccessAt":"2026-11-13T12:57:12.0535039+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:57:12.1370926+00:00","snapshotPublishedAt":"2026-11-13T12:35:15+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-8106b486b70c4e0a972457e9bec940ae","complete":false,"records":13795,"lastAttemptAt":"2026-11-13T13:08:46.7498468+00:00","lastSuccessAt":"2026-11-13T13:08:46.746+00:00","error":"412 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-13T13:08:46.746+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13087,"expectedIdentifiers":13848,"failedIdentifiers":412},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-13T12:59:11.9732431+00:00","complete":true,"records":1123,"lastAttemptAt":"2026-11-13T12:59:11.9732431+00:00","lastSuccessAt":"2026-11-13T12:59:12.1237796+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:12.1237798+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-18b27772e3264b22ab6b919eb23a22fd","complete":true,"records":13795,"lastAttemptAt":"2026-11-13T12:59:14.4637385+00:00","lastSuccessAt":"2026-11-13T12:59:14.459+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:14.459+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13848,"expectedIdentifiers":13848,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-93e76d404e1aeb6a7e8902f5ffa06211fc86dea3b1958e297abb2668aa5e6e8c","complete":true,"records":9952,"lastAttemptAt":"2026-11-13T12:59:07.8110438+00:00","lastSuccessAt":"2026-11-12T23:19:15.5239119+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:07.8110438+00:00","snapshotPublishedAt":"2026-11-12T23:03:02+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-4d60731753a2f72e455d1086e7203d0ef10843936dcc1cf2b45135e2caa204b0","complete":true,"records":2012,"lastAttemptAt":"2026-11-13T12:57:12.2985214+00:00","lastSuccessAt":"2026-11-12T18:16:50.7862525+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:57:12.2985214+00:00","snapshotPublishedAt":"2026-11-12T17:48:11+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-ab4ad5f59937c0596645e186474e26d2fffbbe6ecc09983ad71f9a0d88918405","complete":true,"records":3129,"lastAttemptAt":"2026-11-13T12:59:11.9406927+00:00","lastSuccessAt":"2026-11-13T12:59:11.7864534+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:11.9406927+00:00","snapshotPublishedAt":"2026-11-13T12:47:49+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-7d9437160a3664a4238cadabbe17e78db87dde648ca4c671841d50155dfa5d6c","complete":true,"records":231770,"lastAttemptAt":"2026-11-13T12:59:07.6810383+00:00","lastSuccessAt":"2026-11-13T12:59:06.1905777+00:00","error":null,"lastVerifiedAt":"2026-11-13T12:59:07.6810383+00:00","snapshotPublishedAt":"2026-11-13T12:33:13+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}