Is next-auth 4.24 vulnerable?
npm · 16 releases from 4.24.0 to 4.24.15 · latest next-auth is 4.24.15 · checked 2 Nov 2026
No known advisories in the last release
next-auth 4.24.15, the last 4.24 release, has no known advisories. 5 advisories affect earlier 4.24.x releases, so update to 4.24.15.
npm install next-auth@4.24.15Fixed within 4.24.x, affecting earlier releases
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
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
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
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
Possible user mocking that bypasses basic authentication
- Affected
- <4.24.5
- Fixed in
- 4.24.5
Which of your client projects are still on next-auth 4.24?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact next-auth version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other next-auth versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.