CVE intelligence and bounded remediation
CVE-2022-35924 — NextAuth.js is a complete open source authentication solution for Next.js applications
NextAuth.js is a complete open source authentication solution for Next.js applications. `next-auth` users who are using the `EmailProvider` either in versions before `4.10.3` or `3.29.10` are affected. If an attacker could forge a request that sent a comma-separated list of emails (eg.: `attacker@attacker.com,victim@victim.com`) to the sign-in endpoint, NextAuth.js would send emails to both the attacker and the victim's e-mail addresses. The attacker could then login as a newly created user with the email being `attacker@attacker.com,victim@victim.com`. This means that basic authorization like `email.endsWith("@victim.com")` in the `signIn` callback would fail to communicate a threat to the developer and would let the attacker bypass authorization, even with an `@attacker.com` address. This vulnerability has been patched in `v4.10.3` and `v3.29.10` by normalizing the email value that is sent to the sign-in endpoint before accessing it anywhere else. We also added a `normalizeIdentifier` callback on the `EmailProvider` configuration, where you can further tweak your requirements for what your system considers a valid e-mail address. (E.g.: strict RFC2821 compliance). Users are advi…
- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Published
- 2022-08-02
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-20, CWE-863
Affected products
- nextauth.js / next-auth
Matched remediation archetype
Authorization bypass, IDOR, and cross-tenant access
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map object and action authorization checks across API, UI, batch, import/export, and background-job paths.
- Identify tenant, ownership, role, and policy boundaries for affected resources and administrative operations.
- Use synthetic fixtures to compare intended access matrices without accessing another user's real data.
Remediate safely
- Enforce server-side authorization at each resource access and state transition using the authenticated principal and trusted tenant context.
- Scope data queries by tenant and ownership; treat client-supplied identifiers, roles, and policy claims as untrusted.
- Add deny-by-default policy tests for horizontal and vertical access across every affected transport.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.