Advisory

GHSA-vqx2-fgx2-5wq9

Also known as: CVE-2026-41248

Summary

Official Clerk JavaScript SDKs: Middleware-based route protection bypass

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

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-04-16 21:28 UTC
Modified
2026-05-05 16:26 UTC

Affected packages and fixes

11 affected packages; all npm · All systems
PackageAffectedFix
@clerk/nextjsintroduced 5.0.0, fixed 5.7.6npm install @clerk/[email protected]
@clerk/nuxtintroduced 1.1.0, fixed 1.13.28npm install @clerk/[email protected]
@clerk/astrointroduced 0.0.1, fixed 1.5.7npm install @clerk/[email protected]
@clerk/sharedintroduced 2.20.17, fixed 2.22.1npm install @clerk/[email protected]
@clerk/nextjsintroduced 6.0.0-snapshot.vb87a27f, fixed 6.39.2npm install @clerk/[email protected]
@clerk/nextjsintroduced 7.0.0, fixed 7.2.1npm install @clerk/[email protected]
@clerk/nuxtintroduced 2.0.0, fixed 2.2.2npm install @clerk/[email protected]
@clerk/astrointroduced 2.0.0-snapshot.v20241206174604, fixed 2.17.10npm install @clerk/[email protected]
@clerk/astrointroduced 3.0.0, fixed 3.0.15npm install @clerk/[email protected]
@clerk/sharedintroduced 3.0.0-canary.v20250225091530, fixed 3.47.4npm install @clerk/[email protected]
@clerk/sharedintroduced 4.0.0, fixed 4.8.1npm install @clerk/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences