@clerk/nuxt Known Vulnerabilities & Fixes
@clerk/nuxt has 3 known security vulnerabilities in npm (Node.js). Upgrade to version 2.2.5 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 2.2.5
Upgrading to 2.2.5 or later resolves all 3 known vulnerabilities in @clerk/nuxt. Run: npm install @clerk/nuxt@2.2.5
Is @clerk/nuxt in your project?
Check if you're affected and upgrade to 2.2.5 to stay secure.
Security Summary
- 5 affected version ranges have been identified across these 3 advisories.
- 100% of known issues have a published fixed version.
- Remediation: npm update @clerk/nuxt
Vulnerabilities
3 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Jul 9, 2025, most recently Apr 30, 2026 (295 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-41248 Official Clerk JavaScript SDKs: Middleware-based route protection bypass | CRITICAL | All versions | 1.13.28, 2.2.2 |
| CVE-2025-53548 @clerk/backend Performs Insufficient Verification of Data Authenticity | HIGH | All versions | 1.7.5 |
| CVE-2026-42349 Clerk has an authorization bypass when combining organization, billing, or reverification checks | HIGH | All versions | 1.13.29, 2.2.5 |
About This Data
Vulnerability data for @clerk/nuxt is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of @clerk/nuxt.