CVE-2021-21310: medium-severity vulnerability in nextauthjs next-auth
Token verification bug in next-auth
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.1epss 1.7%
NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
Affected products
nextauthjs · next-authRelated CVEs — nextauthjs next-auth
In the same product, most dangerous first.
CVE-2022-31093HIGHImproper Handling of `callbackUrl` parameter in next-authEPSS 1.7%CVE-2022-35924CRITICALVerification requests (magic link) sent to unwanted emailsEPSS 1.5%CVE-2022-31127HIGHImproper handling of email input in next-authEPSS 1.1%CVE-2026-73418HIGHNextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headersEPSS 0.9%CVE-2022-24858MEDIUMDefault redirect callback vulnerable to open redirectsEPSS 0.8%CVE-2026-73420CRITICALNextAuth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypassEPSS 0.7%