@clerk/nextjs vulnerabilities
Clerk SDK for NextJS
- Registry
- npm
- Latest
- 7.9.20
- License
- MIT
4 known advisories
The latest version, 7.9.20, is not affected by any of them. Projects on older versions may be.
npm install @clerk/nextjs@7.9.20Security advisories for @clerk/nextjs
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
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
@clerk/backend Performs Insufficient Verification of Data Authenticity
- Affected
- >=6.2.10 <6.23.3
- Fixed in
- 6.23.3
@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 still run an old @clerk/nextjs?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.