chore(deps): update dependency @clerk/nextjs to v6.39.3 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@clerk/nextjs (source)	6.36.5 → 6.39.3

---

Official Clerk JavaScript SDKs: Middleware-based route protection bypass

CVE-2026-41248 / GHSA-vqx2-fgx2-5wq9

More information

Details

Summary

createRouteMatcher in @clerk/nextjs, @clerk/nuxt, and @clerk/astro can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers.

Sessions are not compromised and no existing user can be impersonated - the bypass only affects the middleware-level gating decision.

Who is affected

All apps using createRouteMatcher should upgrade to the patched versions. Patches are drop-in with no API changes. The information below describes the scope of the bypass and helps you understand whether you are potentially affected, but is not a reason to delay the upgrade.

Apps relying only on middleware gating via createRouteMatcher are affected, because a crafted request can skip middleware checks and reach downstream handlers (API routes, server components, etc.). This middleware pattern permits the bypass:

// Next.js example, equivalent patterns exist in Nuxt and Astro
const isProtectedRoute = createRouteMatcher(['/admin(.*)']);

export default clerkMiddleware(async (auth, req) => {
  if (isProtectedRoute(req)) {
    await auth.protect();
  }
});

That said, the bypass is limited to the middleware-level route-matching gate. clerkMiddleware still authenticates the request and auth() reflects the real authentication state of the caller. Auth checks performed inside your route handlers, server components, or server actions continue to work correctly and are not affected. Whether your app is affected in practice depends on whether you have those downstream checks.

External APIs that authenticate each request with a token are also unaffected on those endpoints, since token verification runs independently.

Additionally, this common middleware pattern correctly blocks the bypass at the middleware layer:

// Next.js example, equivalent patterns exist in Nuxt and Astro
const isPublicRoute = createRouteMatcher(['/docs(.*)']);

export default clerkMiddleware(async (auth, req) => {
  if (!isPublicRoute(req)) {
    await auth.protect();
  }
});

@clerk/shared is usually not imported directly in application code, but if you import createPathMatcher from an affected @clerk/shared version, you are also affected. Run npm why @​clerk/shared (or your package manager's equivalent) to check your installed version.

Recommended actions

Install the patched version for your framework (pick the one matching your current major):

@clerk/nextjs

• v7.x: fixed in 7.2.1
• v6.x: fixed in 6.39.2
• v5.x: fixed in 5.7.6

@clerk/nuxt

• v2.x: fixed in 2.2.2
• v1.x: fixed in 1.13.28

@clerk/astro

• v3.x: fixed in 3.0.15
• v2.x: fixed in 2.17.10
• v1.x: fixed in 1.5.7

@clerk/shared

• v4.x: fixed in 4.8.1
• v3.x: fixed in 3.47.4
• v2.x: fixed in 2.22.1

Workaround

If you cannot upgrade immediately, adding server-side auth checks (auth()) inside your route handlers, server components, or server actions provides defense-in-depth against this bypass.

Timeline

This issue was reported on 13 APR 2026, patched on 15 APR 2026, and publicly disclosed on 15 APR 2026.

Thanks to Christiaan Swiers for the responsible disclosure of this vulnerability.

Severity

• CVSS Score: 9.1 / 10 (Critical)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

• https://github.com/clerk/javascript/security/advisories/GHSA-vqx2-fgx2-5wq9
• https://nvd.nist.gov/vuln/detail/CVE-2026-41248
• https://github.com/advisories/GHSA-vqx2-fgx2-5wq9

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Clerk has an authorization bypass when combining organization, billing, or reverification checks

CVE-2026-42349 / GHSA-w24r-5266-9c3c

More information

Details

Summary

has(), auth.protect(), and related authorization predicates in @clerk/shared, @clerk/nextjs, @clerk/backend, and other framework SDKs can return true for certain combined authorization checks when the result should be false, allowing a gated action to proceed for a user who does not satisfy the full set of requested conditions.

Sessions are not compromised and no existing user can be impersonated. The bypass is limited to the authorization decision returned by the predicate. clerkMiddleware continues to authenticate requests correctly, auth() reflects the real authentication state, and token verification is unaffected.

Who is affected

All apps that combine more than one authorization dimension in a single has() or auth.protect() call should upgrade to the patched versions. Patches are drop-in with no API changes. The information below describes the scope of the bypass and helps developers understand whether their apps are potentially affected, but is not a reason to delay the upgrade.

This call shape can be bypassed if certain conditions are met: a has() or auth.protect() call that combines a reverification check with any of role, permission, feature, or plan, or that combines a billing check (feature or plan) with a role or permission check.

// Reverification combined with role / permission / feature / plan
await auth.protect({ permission: 'org:settings:delete', reverification: 'strict' });
const canAct = has({ role: 'org:admin', reverification: 'strict' });

// Billing (feature / plan) combined with role / permission
const canAct = has({ permission: 'org:admin', feature: 'premium' });

Single-condition checks are not affected and continue to fail closed as expected:

await auth.protect({ permission: 'org:settings:delete' });
has({ reverification: 'strict' });

The callback form of auth.protect is not affected unless the callback itself invokes one of the affected shapes:

await auth.protect(has => has({ permission: 'org:X' }) && has({ reverification: 'strict' }));

App patterns that rely only on single-condition checks, or that combine them via the callback form, are unaffected. Authentication, session state, and token verification continue to work correctly regardless of this bypass.

@clerk/shared is usually not imported directly in application code, but the fix lives there and reaches an app through its framework package. If developers import createCheckAuthorization from @clerk/shared directly, their apps are also affected. Run npm why @​clerk/shared (or the app's package manager's equivalent) to check the installed version.

Additional auth.protect() bypass

A second, related bypass lives in @clerk/nextjs: auth.protect() silently discarded authorization params (role, permission, feature, plan, reverification) whenever the same argument object also contained unauthenticatedUrl, unauthorizedUrl, or token.

Recommended actions

Upgrade to the latest patch release of the consuming app's framework package on its current major. Both Core 2 and Core 3 release lines have patches. See the "Affected packages" section above for the exact vulnerable ranges and patched versions per package.

If a consuming app pins @clerk/clerk-js directly, upgrade it to the patched version. Most apps load @clerk/clerk-js from Clerk's CDN through their framework package and will receive the fix automatically, with no upgrade step required.

Workaround

If developers cannot upgrade immediately, split combined has() or auth.protect() calls into sequential single-condition checks:

// Replace
await auth.protect({ permission: 'org:X', reverification: 'strict' });
// With
await auth.protect({ reverification: 'strict' });
await auth.protect({ permission: 'org:X' });

Each single-condition check fails closed as expected, so evaluating them independently and denying if either fails produces the correct result.

Timeline

This issue was reported on 18 APR 2026, patched on 22 APR 2026, and publicly disclosed on 22 APR 2026.

Thanks to AISafe for the responsible disclosure of this vulnerability.

Severity

• CVSS Score: 7.6 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/clerk/javascript/security/advisories/GHSA-w24r-5266-9c3c
• https://github.com/advisories/GHSA-w24r-5266-9c3c

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

clerk/javascript (@​clerk/nextjs)

v6.39.2

Compare Source

Patch Changes

• Normalize URL paths in createPathMatcher to prevent route protection bypass (#​8310) by @​nikosdouvlis

• Updated dependencies [2c14f0e]:

  • @​clerk/shared@​3.47.4
  • @​clerk/backend@​2.33.2
  • @​clerk/clerk-react@​5.61.5
  • @​clerk/types@​4.101.22

v6.39.1

Compare Source

Patch Changes

• Updated dependencies [e5f213f]:
  • @​clerk/shared@​3.47.3
  • @​clerk/backend@​2.33.1
  • @​clerk/clerk-react@​5.61.4
  • @​clerk/types@​4.101.21

v6.39.0

Compare Source

Minor Changes

• Added support for JWT token format when creating and verifying machine-to-machine (M2M) tokens. This enables fully networkless verification when using the public JWT key. (#​7883) by @​wobsoriano

  Creating a JWT-format M2M token

  const clerkClient = createClerkClient({
    machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY,
  });
  
  const m2mToken = await clerkClient.m2m.createToken({
    tokenFormat: 'jwt',
  });
  
  console.log('M2M token created:', m2mToken.token);

  Verifying a token

  const clerkClient = createClerkClient({
    machineSecretKey: process.env.CLERK_MACHINE_SECRET_KEY,
  });
  
  const authHeader = req.headers.get('Authorization');
  const token = authHeader.slice(7);
  
  const verified = await clerkClient.m2m.verify(token);
  
  console.log('Verified M2M token:', verified);

  Networkless verification

  const clerkClient = createClerkClient({
    jwtKey: process.env.CLERK_JWT_KEY,
  });
  
  const authHeader = req.headers.get('Authorization');
  const token = authHeader.slice(7);
  
  const verified = await clerkClient.m2m.verify(token);
  
  console.log('Verified M2M token:', verified);

Patch Changes

• Updated dependencies [76a5a1b, 7955e9d, 51bc9a9]:
  • @​clerk/backend@​2.33.0
  • @​clerk/shared@​3.47.2
  • @​clerk/clerk-react@​5.61.3
  • @​clerk/types@​4.101.20

v6.38.3

Compare Source

Patch Changes

• Updated dependencies [8a0c404]:
  • @​clerk/shared@​3.47.1
  • @​clerk/backend@​2.32.2
  • @​clerk/clerk-react@​5.61.2
  • @​clerk/types@​4.101.19

v6.38.2

Compare Source

Patch Changes

• Updated dependencies [c15c8a2]:
  • @​clerk/backend@​2.32.1

v6.38.1

Compare Source

Patch Changes

• Updated dependencies [c00c524, 9c935ad]:
  • @​clerk/shared@​3.47.0
  • @​clerk/backend@​2.32.0
  • @​clerk/clerk-react@​5.61.1
  • @​clerk/types@​4.101.18

v6.38.0

Compare Source

Minor Changes

• Introduces MFA setup session task for handling require MFA after sign-in and sign-up (#​7851) by @​octoper

Patch Changes

• Fix infinite handshake redirect loop when deploying Next.js apps with Clerk development instances to Netlify (#​7876) by @​mauricioabreu

• Updated dependencies [71bd53c, 935f780, 2471e31]:

  • @​clerk/clerk-react@​5.61.0
  • @​clerk/shared@​3.46.0
  • @​clerk/backend@​2.31.2
  • @​clerk/types@​4.101.17

v6.37.5

Compare Source

Patch Changes

• Updated dependencies [b17e4bb]:
  • @​clerk/shared@​3.45.1
  • @​clerk/backend@​2.31.1
  • @​clerk/clerk-react@​5.60.2
  • @​clerk/types@​4.101.16

v6.37.4

Compare Source

Patch Changes

• Updated dependencies [35bcbd1, 5740640, 03c61c1]:
  • @​clerk/shared@​3.45.0
  • @​clerk/backend@​2.31.0
  • @​clerk/clerk-react@​5.60.1
  • @​clerk/types@​4.101.15

v6.37.3

Compare Source

Patch Changes

• Updated dependencies [a726252]:
  • @​clerk/backend@​2.30.1

v6.37.2

Compare Source

Patch Changes

• Fixed an issue where JWT OAuth access tokens where not treated as a machine token (#​7756) by @​wobsoriano

• Updated dependencies [7917ff4, b0d28c1]:

  • @​clerk/backend@​2.30.0

v6.37.1

Compare Source

Patch Changes

• Updated dependencies [559cd84]:
  • @​clerk/backend@​2.29.7

v6.37.0

Compare Source

Minor Changes

• Export useOrganizationCreationDefaults hook to fetch suggested organization name and logo from default naming rules (#​7690) by @​LauraBeatris

Patch Changes

• Updates middleware location check to account for proxy.ts in next 16+ applications. (#​7269) by @​alexcarpenter

• Updated dependencies [64a35f7]:

  • @​clerk/shared@​3.44.0
  • @​clerk/clerk-react@​5.60.0
  • @​clerk/backend@​2.29.6
  • @​clerk/types@​4.101.14

v6.36.10

Compare Source

Patch Changes

• Updated dependencies [b7a4e1e]:
  • @​clerk/shared@​3.43.2
  • @​clerk/backend@​2.29.5
  • @​clerk/clerk-react@​5.59.6
  • @​clerk/types@​4.101.13

v6.36.9

Compare Source

Patch Changes

• Updated dependencies [e995cc3]:
  • @​clerk/shared@​3.43.1
  • @​clerk/clerk-react@​5.59.5
  • @​clerk/backend@​2.29.4
  • @​clerk/types@​4.101.12

v6.36.8

Compare Source

Patch Changes

• Add image CDNs to the connect-src Content Security Policy directive (#​7611) by @​LauraBeatris

• Updated dependencies [c3ff1f8, 271ddeb, 57ff2fb]:

  • @​clerk/backend@​2.29.3
  • @​clerk/shared@​3.43.0
  • @​clerk/clerk-react@​5.59.4
  • @​clerk/types@​4.101.11

v6.36.7

Compare Source

Patch Changes

• Updated dependencies [6b26afc]:
  • @​clerk/backend@​2.29.2
  • @​clerk/clerk-react@​5.59.3

v6.36.6

Compare Source

Patch Changes

• Updated dependencies [9320c4f, a4e6932]:
  • @​clerk/backend@​2.29.1
  • @​clerk/shared@​3.42.0
  • @​clerk/clerk-react@​5.59.3
  • @​clerk/types@​4.101.10

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat-io	Ready	Preview, Comment	Apr 30, 2026 11:05pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​clerk/​nextjs@​6.36.5 ⏵ 6.39.3	-21	+75	+1	+1

View full report