CVE-2026-42349

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-42349 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.47.5, 4.8.3, 2.33.3, 3.2.14, 6.39.3, 7.2.4, 5.125.10, 6.7.5, 5.61.6, 6.4.3, 1.17.21, 2.0.16, 2.17.11, 3.0.18, 1.13.29, 2.2.5, 2.19.36, 3.2.2, 2.4.13, 3.1.4, 0.29.11, 1.1.4, 2.9.15, 3.1.15, 2.6.31, 3.1.16, 1.7.79, 2.1.6, 0.1.16); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-42349? CVE-2026-42349 is a high-severity incorrect authorization vulnerability in @clerk/shared (npm), affecting versions >= 3.0.0, <= 3.47.4. It is fixed in 3.47.5, 4.8.3, 2.33.3, 3.2.14, 6.39.3, 7.2.4, 5.125.10, 6.7.5, 5.61.6, 6.4.3, 1.17.21, 2.0.16, 2.17.11, 3.0.18, 1.13.29, 2.2.5, 2.19.36, 3.2.2, 2.4.13, 3.1.4, 0.29.11, 1.1.4, 2.9.15, 3.1.15, 2.6.31, 3.1.16, 1.7.79, 2.1.6, 0.1.16. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-42349? CVE-2026-42349 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-42349?
   • @clerk/shared (npm) (versions >= 3.0.0, <= 3.47.4)
   • @clerk/backend (npm) (versions >= 2.0.0, <= 2.33.2)
   • @clerk/nextjs (npm) (versions >= 6.0.0, <= 6.39.2)
   • @clerk/clerk-js (npm) (versions >= 5.22.0, <= 5.125.9)
   • @clerk/clerk-react (npm) (versions >= 5.9.0, <= 5.61.5)
   • @clerk/react (npm) (versions >= 6.0.0, <= 6.4.2)
   • @clerk/vue (npm) (versions >= 1.0.0, <= 1.17.20)
   • @clerk/astro (npm) (versions >= 2.0.0, <= 2.17.10)
   • @clerk/nuxt (npm) (versions >= 1.0.0, <= 1.13.28)
   • @clerk/clerk-expo (npm) (versions >= 2.2.11, <= 2.19.35)
   • @clerk/expo (npm) (versions >= 3.0.0, <= 3.2.1)
   • @clerk/react-router (npm) (versions >= 0.0.1, <= 2.4.12)
   • @clerk/tanstack-react-start (npm) (versions >= 0.0.1, <= 0.29.10)
   • @clerk/chrome-extension (npm) (versions >= 1.3.5, <= 2.9.14)
   • @clerk/fastify (npm) (versions >= 1.0.42, <= 2.6.30)
   • @clerk/express (npm) (versions >= 0.1.0, <= 1.7.78)
   • @clerk/hono (npm) (versions >= 0.0.2, <= 0.1.15)
4. Is there a fix for CVE-2026-42349? Yes. CVE-2026-42349 is fixed in 3.47.5, 4.8.3, 2.33.3, 3.2.14, 6.39.3, 7.2.4, 5.125.10, 6.7.5, 5.61.6, 6.4.3, 1.17.21, 2.0.16, 2.17.11, 3.0.18, 1.13.29, 2.2.5, 2.19.36, 3.2.2, 2.4.13, 3.1.4, 0.29.11, 1.1.4, 2.9.15, 3.1.15, 2.6.31, 3.1.16, 1.7.79, 2.1.6, 0.1.16. Upgrade to this version or later.
5. Is CVE-2026-42349 exploitable, and should I be worried? Whether CVE-2026-42349 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-42349 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-42349?
   • Upgrade @clerk/shared to 3.47.5 or later
   • Upgrade @clerk/shared to 4.8.3 or later
   • Upgrade @clerk/backend to 2.33.3 or later
   • Upgrade @clerk/backend to 3.2.14 or later
   • Upgrade @clerk/nextjs to 6.39.3 or later
   • Upgrade @clerk/nextjs to 7.2.4 or later
   • Upgrade @clerk/clerk-js to 5.125.10 or later
   • Upgrade @clerk/clerk-js to 6.7.5 or later
   • Upgrade @clerk/clerk-react to 5.61.6 or later
   • Upgrade @clerk/react to 6.4.3 or later
   • Upgrade @clerk/vue to 1.17.21 or later
   • Upgrade @clerk/vue to 2.0.16 or later
   • Upgrade @clerk/astro to 2.17.11 or later
   • Upgrade @clerk/astro to 3.0.18 or later
   • Upgrade @clerk/nuxt to 1.13.29 or later
   • Upgrade @clerk/nuxt to 2.2.5 or later
   • Upgrade @clerk/clerk-expo to 2.19.36 or later
   • Upgrade @clerk/expo to 3.2.2 or later
   • Upgrade @clerk/react-router to 2.4.13 or later
   • Upgrade @clerk/react-router to 3.1.4 or later
   • Upgrade @clerk/tanstack-react-start to 0.29.11 or later
   • Upgrade @clerk/tanstack-react-start to 1.1.4 or later
   • Upgrade @clerk/chrome-extension to 2.9.15 or later
   • Upgrade @clerk/chrome-extension to 3.1.15 or later
   • Upgrade @clerk/fastify to 2.6.31 or later
   • Upgrade @clerk/fastify to 3.1.16 or later
   • Upgrade @clerk/express to 1.7.79 or later
   • Upgrade @clerk/express to 2.1.6 or later
   • Upgrade @clerk/hono to 0.1.16 or later