Authorization bypass via unnormalized email recipient lists
Published Aug 2, 2022 · Updated Apr 23, 2025
Improper input validation in Auth.js NextAuth.js 3.29.9 and earlier and 4.0.0 through 4.10.2 allows remote attackers to bypass authorization. The EmailProvider sign-in route passes a comma-separated identifier to the mailer and authorization callback without first reducing it to one address. An unauthenticated request can receive the same magic link as a victim and create a composite-email account that passes suffix-based domain checks.
Summary
What happened
Improper input validation in Auth.js NextAuth.js 3.29.9 and earlier and 4.0.0 through 4.10.2 allows remote attackers to bypass authorization. The EmailProvider sign-in route passes a comma-separated identifier to the mailer and authorization callback without first reducing it to one address. An unauthenticated request can receive the same magic link as a victim and create a composite-email account that passes suffix-based domain checks.
The record
- CVE
- CVE-2022-35924
- Published
- Aug 2, 2022
- Updated
- Apr 23, 2025
- Vendor
- Auth.js
- Product
- NextAuth.js
- Classifications
- CWE-20, T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 3.29.10
- Affected versionversion=>= 4.0.0, < 4.10.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.
Public exploit references
- Comma-separated email identifier requestproof of concept · demonstrated
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