next-auth vulnerabilities

Authentication for Next.js

Registry
npm
Latest
4.24.15
License
ISC

14 known advisories

The latest version, 4.24.15, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install next-auth@4.24.15

Security advisories for next-auth

  • CriticalGHSA-8fpg-xm3f-6cx323 Jul 2026

    Auth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error)

    Affected
    >=5.0.0-beta.0 <5.0.0-beta.32
    Fixed in
    5.0.0-beta.32
  • HighGHSA-xmf8-cvqr-rfgj23 Jul 2026

    Auth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers

    Affected
    >=5.0.0-beta.0 <5.0.0-beta.32 · >=4.0.6 <4.24.15
    Fixed in
    4.24.15, 5.0.0-beta.32
  • CriticalGHSA-7rqj-j65f-68wh23 Jul 2026

    Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass

    Affected
    >=4.10.3 <4.24.15 · >=5.0.0-beta.1 <5.0.0-beta.32
    Fixed in
    4.24.15, 5.0.0-beta.32
  • MediumGHSA-x445-f3h2-j27923 Jul 2026

    Auth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them

    Affected
    >=5.0.0-beta.1 <5.0.0-beta.32 · <4.24.15
    Fixed in
    4.24.15, 5.0.0-beta.32
  • MediumGHSA-5jpx-9hw9-2fx429 Oct 2025

    NextAuthjs Email misdelivery Vulnerability

    Affected
    <4.24.12 · >=5.0.0-beta.0 <5.0.0-beta.30
    Fixed in
    4.24.12, 5.0.0-beta.30
  • MediumGHSA-v64w-49xw-qq8920 Nov 2023

    Possible user mocking that bypasses basic authentication

    Affected
    <4.24.5
    Fixed in
    4.24.5
  • HighGHSA-7r7x-4c4q-c4qf13 Mar 2023

    Missing proper state, nonce and PKCE checks for OAuth authentication

    Affected
    <4.20.1
    Fixed in
    4.20.1
  • LowGHSA-p6mm-27gq-9v3p6 Aug 2022

    next-auth before v4.10.2 and v3.29.9 leaks excessive information into log

    Affected
    <3.29.9 · >=4.0.0 <4.10.2
    Fixed in
    3.29.9, 4.10.2
  • CriticalGHSA-xv97-c62v-45872 Aug 2022

    NextAuth.js before 4.10.3 and 3.29.10 sending verification requests (magic link) to unwanted emails

    Affected
    >=4.0.0 <4.10.3 · <3.29.10
    Fixed in
    3.29.10, 4.10.3
  • HighGHSA-pgjx-7f9g-94636 Jul 2022

    Improper handling of email input

    Affected
    <3.29.8 · >=4.0.0 <4.9.0
    Fixed in
    3.29.8, 4.9.0
  • HighGHSA-g5fm-jp9v-243221 Jun 2022

    Improper Handling of `callbackUrl` parameter in next-auth

    Affected
    <3.29.5 · >=4.0.0 <4.5.0
    Fixed in
    3.29.5, 4.5.0
  • MediumGHSA-q2mx-j4x2-2h7424 May 2022

    URL Redirection to Untrusted Site ('Open Redirect') in next-auth

    Affected
    <3.29.3 · >=4.0.0 <4.3.3
    Fixed in
    3.29.3, 4.3.3
  • MediumGHSA-f9wg-5f46-cjmw22 Apr 2022

    NextAuth.js default redirect callback vulnerable to open redirects

    Affected
    <3.29.2 · >=4.0.0 <4.3.2
    Fixed in
    3.29.2, 4.3.2
  • LowGHSA-pg53-56cg-4m8q11 Feb 2021

    Token verification bug in next-auth

    Affected
    <3.3.0
    Fixed in
    3.3.0

Which of your client projects still run an old next-auth?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.