@clerk/nextjs vulnerabilities
Clerk SDK for NextJS
- Registry
- npm
- Latest
- 7.9.26
- License
- MIT
4 known advisories
The latest version, 7.9.26, is not affected by any of them. Projects on older versions may be.
npm install @clerk/nextjs@7.9.26Is your project on an affected @clerk/nextjs?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security 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
Is your @clerk/nextjs version vulnerable?
- @clerk/nextjs 7.9No known advisories in 7.9.26
- @clerk/nextjs 7.8No known advisories in 7.8.4
- @clerk/nextjs 7.7No known advisories in 7.7.9
- @clerk/nextjs 7.6No known advisories in 7.6.5
- @clerk/nextjs 7.5No known advisories in 7.5.22
- @clerk/nextjs 7.4No known advisories in 7.4.3
- @clerk/nextjs 6.39No known advisories in 6.39.9
- @clerk/nextjs 6.382 advisories in 6.38.3
- @clerk/nextjs 6.372 advisories in 6.37.5
- @clerk/nextjs 6.362 advisories in 6.36.10
- @clerk/nextjs 6.352 advisories in 6.35.6
- @clerk/nextjs 6.342 advisories in 6.34.6
- @clerk/nextjs 5.7No known advisories in 5.7.6
- @clerk/nextjs 5.61 advisory in 5.6.4
- @clerk/nextjs 5.51 advisory in 5.5.5
- @clerk/nextjs 5.41 advisory in 5.4.1
- @clerk/nextjs 5.31 advisory in 5.3.7
- @clerk/nextjs 5.21 advisory in 5.2.14
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.