Categories
CVE-2026-42349 high CVSS 8.1

Vulnerability in @clerk/shared (CVE-2026-42349)

Summary

Vulnerability in @clerk/shared (CVE-2026-42349). Confidential information can be exposed externally. Exploitable via clerkMiddleware. Mitigation: upgrade to 4.8.3 or later.

Original description

The description as published by the source.

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({…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-42349 has been found in @clerk/shared.
Attackers can target a specific entry point like clerkMiddleware over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade @clerk/shared to 4.8.3 or later.
If unsure, ask your IT team or search "@clerk/shared CVE-2026-42349" on the vendor's site.

CVE-2026-42349 (@clerk/shared) — CWE-754 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: clerkMiddleware / reverification / role / permission
Patched: 4.8.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-754) exists in @clerk/shared. Attackers reach the vulnerable code path via clerkMiddleware.

📍 Affected scope

Check the vendor advisory for the affected versions of @clerk/shared. Attack surface: clerkMiddleware / reverification / role / permission.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.8.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@clerk/shared' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@clerk/shared' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @clerk/shared を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade @clerk/shared to 4.8.3

    ステージング環境で 4.8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @clerk/shared
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.8.3"}]}]
npm @clerk/backend
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.2.14"}]}]
npm @clerk/nextjs
[{"type":"SEMVER","events":[{"introduced":"7.0.0"},{"fixed":"7.2.4"}]}]
npm @clerk/clerk-js
[{"type":"SEMVER","events":[{"introduced":"6.0.0"},{"fixed":"6.7.5"}]}]
npm @clerk/clerk-react
[{"type":"SEMVER","events":[{"introduced":"5.9.0"},{"fixed":"5.61.6"}]}]
npm @clerk/react
[{"type":"SEMVER","events":[{"introduced":"6.0.0"},{"fixed":"6.4.3"}]}]
npm @clerk/vue
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.0.16"}]}]
npm @clerk/astro
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.0.18"}]}]
npm @clerk/nuxt
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.2.5"}]}]
npm @clerk/clerk-expo
[{"type":"SEMVER","events":[{"introduced":"2.2.11"},{"fixed":"2.19.36"}]}]
npm @clerk/expo
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.2.2"}]}]
npm @clerk/react-router
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.1.4"}]}]
npm @clerk/tanstack-react-start
[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.1.4"}]}]
npm @clerk/chrome-extension
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.1.15"}]}]
npm @clerk/fastify
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.1.16"}]}]
npm @clerk/express
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.1.6"}]}]
npm @clerk/hono
[{"type":"SEMVER","events":[{"introduced":"0.0.2"},{"fixed":"0.1.16"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details