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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@clerk/react (source)	6.1.2 → 6.4.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

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://nvd.nist.gov/vuln/detail/CVE-2026-42349
• https://github.com/clerk/javascript

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

---

Release Notes

clerk/javascript (@​clerk/react)

v6.4.3

Patch Changes

• Updated dependencies [d52b311]:
  • @​clerk/shared@4.8.3

v6.4.2

Compare Source

Patch Changes

• Updated dependencies [c7b0f47, 34762e8]:
  • @​clerk/shared@4.8.2

v6.4.1

Patch Changes

• Updated dependencies [b0b6675]:
  • @​clerk/shared@4.8.1

v6.4.0

Minor Changes

• Introduce internal <OAuthConsent /> component for rendering a zero-config OAuth consent screen on an OAuth authorize redirect page. (#​8289) by @​wobsoriano

  Usage example:

  import { OAuthConsent } from '@clerk/nextjs';
  
  export default function OAuthConsentPage() {
    return <OAuthConsent />;
  }

Patch Changes

• Updated dependencies [dc2de16]:
  • @​clerk/shared@4.8.0

v6.3.0

Compare Source

Minor Changes

• Add OAuthApplication resource and getConsentInfo() method for retrieving OAuth consent information, enabling custom OAuth consent flows. (#​8275) by @​jfoshee

• Introduce internal useOAuthConsent() hook for fetching OAuth consent screen metadata for the signed-in user. (#​8286) by @​jfoshee

Patch Changes

• Updated dependencies [3fd586d, f9ff9e9]:
  • @​clerk/shared@4.7.0

v6.2.1

Compare Source

Patch Changes

• Updated dependencies [fdac10e, 4e3cb0a, aa32bbc]:
  • @​clerk/shared@4.6.0

v6.2.0

Compare Source

Minor Changes

• API keys is now generally available. (#​8059) by @​wobsoriano

<APIKeys /> component

import { APIKeys } from '@clerk/react';

export default function Page() {
  return <APIKeys />;
}

useAPIKeys() hook

import { useAPIKeys } from '@clerk/react';

export default function CustomAPIKeys() {
  const { data, isLoading, page, pageCount, fetchNext, fetchPrevious } = useAPIKeys({
    pageSize: 10,
    initialPage: 1,
  });

  if (isLoading) return <div>Loading...</div>;

  return (
    <ul>
      {data?.map(key => (
        <li key={key.id}>{key.name}</li>
      ))}
    </ul>
  );
}

Patch Changes

• Updated dependencies [2c06a5f]:
  • @​clerk/shared@4.5.0

v6.1.4

Compare Source

Patch Changes

• Updated dependencies [9a00a1c, 00715a6, b8c73d3, 1827b50, 7707a31]:
  • @​clerk/shared@4.4.0

v6.1.3

Compare Source

Patch Changes

• Deprecate the signOutOptions prop on <SignOutButton /> in favor of top-level redirectUrl and sessionId props. The signOutOptions prop still works but now emits a deprecation warning. (#​8147) by @​jacekradko

---

Configuration

📅 Schedule: (in timezone America/Denver)

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

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

♻ Rebasing: Whenever PR becomes conflicted, 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
ai-identity-landing	Ready	Preview	Sep 10, 2026 6:11pm UTC
dashboard	Ready	Preview	Sep 10, 2026 6:11pm UTC