pwnmyvibecode_

Clerk vulnerabilities and security advisories

The newest reviewed advisories for @clerk/nextjs, @clerk/clerk-react, @clerk/backend, @clerk/clerk-js, @clerk/express, @clerk/shared and @clerk/clerk-sdk-node on npm. Each one shows which versions are affected, which version fixes it, and a prompt that has your AI agent check your project and upgrade only if it needs to.

Get an email when Clerk has a new one

Email alerts are coming soon. This page updates every hour.

$ latest 6 · 5 critical, high or exploited

  • highApr 30, 2026

    Clerk has an authorization bypass when combining organization, billing, or reverification checks

    • @clerk/shared >= 3.0.0, <= 3.47.4 · fixed in 3.47.5
    • @clerk/shared >= 4.0.0, <= 4.8.2 · fixed in 4.8.3
    • @clerk/backend >= 2.0.0, <= 2.33.2 · fixed in 2.33.3
    • @clerk/backend >= 3.0.0, <= 3.2.13 · fixed in 3.2.14
    • @clerk/nextjs >= 6.0.0, <= 6.39.2 · fixed in 6.39.3
    • @clerk/nextjs >= 7.0.0, <= 7.2.3 · fixed in 7.2.4
    • @clerk/clerk-js >= 5.22.0, <= 5.125.9 · fixed in 5.125.10
    • @clerk/clerk-js >= 6.0.0, <= 6.7.4 · fixed in 6.7.5
    • @clerk/clerk-react >= 5.9.0, <= 5.61.5 · fixed in 5.61.6
    • @clerk/express >= 0.1.0, <= 1.7.78 · fixed in 1.7.79
    • @clerk/express >= 2.0.0, <= 2.1.5 · fixed in 2.1.6
    GHSA-w24r-5266-9c3cCVE-2026-42349
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-w24r-5266-9c3c (CVE-2026-42349), severity high
What it is: Clerk has an authorization bypass when combining organization, billing, or reverification checks
Affected packages:
- @clerk/shared: affected versions >= 3.0.0, <= 3.47.4. Fixed in 3.47.5.
- @clerk/shared: affected versions >= 4.0.0, <= 4.8.2. Fixed in 4.8.3.
- @clerk/backend: affected versions >= 2.0.0, <= 2.33.2. Fixed in 2.33.3.
- @clerk/backend: affected versions >= 3.0.0, <= 3.2.13. Fixed in 3.2.14.
- @clerk/nextjs: affected versions >= 6.0.0, <= 6.39.2. Fixed in 6.39.3.
- @clerk/nextjs: affected versions >= 7.0.0, <= 7.2.3. Fixed in 7.2.4.
- @clerk/clerk-js: affected versions >= 5.22.0, <= 5.125.9. Fixed in 5.125.10.
- @clerk/clerk-js: affected versions >= 6.0.0, <= 6.7.4. Fixed in 6.7.5.
- @clerk/clerk-react: affected versions >= 5.9.0, <= 5.61.5. Fixed in 5.61.6.
- @clerk/express: affected versions >= 0.1.0, <= 1.7.78. Fixed in 1.7.79.
- @clerk/express: affected versions >= 2.0.0, <= 2.1.5. Fixed in 2.1.6.
Details: https://github.com/advisories/GHSA-w24r-5266-9c3c

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.
  • criticalApr 16, 2026

    Official Clerk JavaScript SDKs: Middleware-based route protection bypass

    • @clerk/nextjs >= 5.0.0, < 5.7.6 · fixed in 5.7.6
    • @clerk/shared >= 2.20.17, < 2.22.1 · fixed in 2.22.1
    • @clerk/nextjs >= 6.0.0-snapshot.vb87a27f, < 6.39.2 · fixed in 6.39.2
    • @clerk/nextjs >= 7.0.0, < 7.2.1 · fixed in 7.2.1
    • @clerk/shared >= 3.0.0-canary.v20250225091530, < 3.47.4 · fixed in 3.47.4
    • @clerk/shared >= 4.0.0, < 4.8.1 · fixed in 4.8.1
    GHSA-vqx2-fgx2-5wq9CVE-2026-41248
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-vqx2-fgx2-5wq9 (CVE-2026-41248), severity critical
What it is: Official Clerk JavaScript SDKs: Middleware-based route protection bypass
Affected packages:
- @clerk/nextjs: affected versions >= 5.0.0, < 5.7.6. Fixed in 5.7.6.
- @clerk/shared: affected versions >= 2.20.17, < 2.22.1. Fixed in 2.22.1.
- @clerk/nextjs: affected versions >= 6.0.0-snapshot.vb87a27f, < 6.39.2. Fixed in 6.39.2.
- @clerk/nextjs: affected versions >= 7.0.0, < 7.2.1. Fixed in 7.2.1.
- @clerk/shared: affected versions >= 3.0.0-canary.v20250225091530, < 3.47.4. Fixed in 3.47.4.
- @clerk/shared: affected versions >= 4.0.0, < 4.8.1. Fixed in 4.8.1.
Details: https://github.com/advisories/GHSA-vqx2-fgx2-5wq9

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.
  • highMar 27, 2026

    Clerk: SSRF in the opt-in clerkFrontendApiProxy feature may leak secret keys to unintended host

    • @clerk/backend >= 3.0.0, <= 3.2.2 · fixed in 3.2.3
    • @clerk/express >= 2.0.0, <= 2.0.6 · fixed in 2.0.7
    GHSA-gjxx-92w9-8v8fCVE-2026-34076
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-gjxx-92w9-8v8f (CVE-2026-34076), severity high
What it is: Clerk: SSRF in the opt-in clerkFrontendApiProxy feature may leak secret keys to unintended host
Affected packages:
- @clerk/backend: affected versions >= 3.0.0, <= 3.2.2. Fixed in 3.2.3.
- @clerk/express: affected versions >= 2.0.0, <= 2.0.6. Fixed in 2.0.7.
Details: https://github.com/advisories/GHSA-gjxx-92w9-8v8f

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.
  • mediumNov 20, 2025

    Clerk-js vulnerable to bypass of OAuth authentication flow by manipulating request at OTP verification stage

    • @clerk/clerk-js <= 5.88.0 · no fix yet
    GHSA-3mm3-wfpv-q85gCVE-2025-63700
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-3mm3-wfpv-q85g (CVE-2025-63700), severity medium
What it is: Clerk-js vulnerable to bypass of OAuth authentication flow by manipulating request at OTP verification stage
Affected packages:
- @clerk/clerk-js: affected versions <= 5.88.0. No fixed version yet.
Details: https://github.com/advisories/GHSA-3mm3-wfpv-q85g

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.
  • highJul 9, 2025

    @clerk/backend Performs Insufficient Verification of Data Authenticity

    • @clerk/backend >= 2.0.0, < 2.4.0 · fixed in 2.4.0
    • @clerk/express >= 1.6.0, < 1.7.4 · fixed in 1.7.4
    • @clerk/nextjs >= 6.2.10, < 6.23.3 · fixed in 6.23.3
    GHSA-9mp4-77wg-rwx9CVE-2025-53548
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-9mp4-77wg-rwx9 (CVE-2025-53548), severity high
What it is: @clerk/backend Performs Insufficient Verification of Data Authenticity
Affected packages:
- @clerk/backend: affected versions >= 2.0.0, < 2.4.0. Fixed in 2.4.0.
- @clerk/express: affected versions >= 1.6.0, < 1.7.4. Fixed in 1.7.4.
- @clerk/nextjs: affected versions >= 6.2.10, < 6.23.3. Fixed in 6.23.3.
Details: https://github.com/advisories/GHSA-9mp4-77wg-rwx9

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.
  • criticalJan 12, 2024

    @clerk/nextjs auth() and getAuth() methods vulnerable to insecure direct object reference (IDOR)

    • @clerk/nextjs >= 4.7.0, < 4.29.3 · fixed in 4.29.3
    GHSA-q6w5-jg5q-47vgCVE-2024-22206
    prompt for your AI agent
    paste into your agent
    A security advisory covers a package this project may use.

Advisory: GHSA-q6w5-jg5q-47vg (CVE-2024-22206), severity critical
What it is: @clerk/nextjs auth() and getAuth() methods vulnerable to insecure direct object reference (IDOR)
Affected packages:
- @clerk/nextjs: affected versions >= 4.7.0, < 4.29.3. Fixed in 4.29.3.
Details: https://github.com/advisories/GHSA-q6w5-jg5q-47vg

Please:
1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
6. Tell me what you changed and which versions are installed now.

From the GitHub Advisory Database, refreshed hourly. Full history on GitHub.

Keeping Clerk patched

  • npm audit (or pnpm audit) lists known vulnerable packages in your lockfile, including ones pulled in by other packages.
  • Turn on Dependabot for your GitHub repo and it opens the upgrade for you when an advisory lands.
  • A patched framework doesn't cover your own setup: headers, cookies and HTTPS. The free check looks at those.