@auth/core vulnerabilities

Authentication for the Web.

Registry
npm
Latest
0.41.3
License
ISC
Source
github.com/nextauthjs/next-auth (opens the source repository in a new tab)

3 known advisories

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

Update to the latest version:npm install @auth/core@0.41.3

Security advisories for @auth/core

  • HighGHSA-xmf8-cvqr-rfgj23 Jul 2026

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

    Affected
    >=0.1.0 <0.41.3
    Fixed in
    0.41.3
  • CriticalGHSA-7rqj-j65f-68wh23 Jul 2026

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

    Affected
    >=0.1.0 <0.41.3
    Fixed in
    0.41.3
  • 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
    <0.41.3
    Fixed in
    0.41.3

Which of your client projects still run an old @auth/core?

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.

Scan a project free, no signupOr connect GitHub to scan every repo

Other npm packages

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