GHSA-w24r-5266-9c3c

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

```ts // 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:

```ts 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:

```ts 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:

```ts // 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.