CVE-2023-27490highCWE-352CWE-384

CVE-2023-27490: high-severity vulnerability in nextauthjs next-auth

Missing proper state, nonce and PKCE checks for OAuth authentication in next-auth

Published · Updated

Follow this CVE+ Monitor next-auth+ Monitor next-auth

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8.1epss 0.5%
NextAuth.js is an open source authentication solution for Next.js applications. `next-auth` applications using OAuth provider versions before `v4.20.1` have been found to be subject to an authentication vulnerability. A bad actor who can read traffic on the victim's network or who is able to social engineer the victim to click a manipulated login link could intercept and tamper with the authorization URL to **log in as the victim**, bypassing the CSRF protection. This is due to a partial failure during a compromised OAuth session where a session code is erroneously generated. This issue has been addressed in version 4.20.1. Users are advised to upgrade. Users unable to upgrade may using Advanced Initialization, manually check the callback request for state, pkce, and nonce against the provider configuration to prevent this issue. See the linked GHSA for details.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Affected products
nextauthjs · next-auth
Related CVEs — nextauthjs next-auth

In the same product, most dangerous first.

CVE-2022-31093HIGHImproper Handling of `callbackUrl` parameter in next-authEPSS 1.7%CVE-2021-21310MEDIUMToken verification bug 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%