Is @clerk/nextjs 6.39 vulnerable?

npm · 9 releases from 6.39.0 to 6.39.8 · latest @clerk/nextjs is 7.9.23 · checked 1 Nov 2026

No known advisories in the last release

@clerk/nextjs 6.39.8, the last 6.39 release, has no known advisories. 2 advisories affect earlier 6.39.x releases, so update to 6.39.8.

Update within 6.39:npm install @clerk/nextjs@6.39.8

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Fixed within 6.39.x, affecting earlier releases

  • HighCVE-2026-42349GHSA-w24r-5266-9c3c30 Apr 2026

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

    Affected
    >=6.0.0 <6.39.3 · >=7.0.0 <7.2.4
    Fixed in
    6.39.3, 7.2.4
  • CriticalCVE-2026-41248GHSA-vqx2-fgx2-5wq916 Apr 2026

    Official Clerk JavaScript SDKs: Middleware-based route protection bypass

    Affected
    >=5.0.0 <5.7.6 · >=6.0.0-snapshot.vb87a27f <6.39.2 · >=7.0.0 <7.2.1
    Fixed in
    5.7.6, 6.39.2, 7.2.1

Which of your client projects are still on @clerk/nextjs 6.39?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact @clerk/nextjs version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other @clerk/nextjs versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.