Is @clerk/nextjs 4.26 vulnerable?

npm · 3 releases from 4.26.0 to 4.26.2 · latest @clerk/nextjs is 7.9.23 · checked 2 Nov 2026

Yes: 1 known advisory

Yes. @clerk/nextjs 4.26.2, the last 4.26 release, is affected by 1 known security advisory (1 critical), including CVE-2024-22206. Upgrade to 4.29.3 or later to fix all of them.

Upgrade with:npm install @clerk/nextjs@4.29.3

Is your project affected?

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

Advisories affecting @clerk/nextjs 4.26.2

  • CriticalCVE-2024-22206GHSA-q6w5-jg5q-47vg12 Jan 2024

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

    Affected
    >=4.7.0 <4.29.3
    Fixed in
    4.29.3

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

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.