Skip to content
Web

CVE-2026-41248

9.1
Critical
EPSS 0.32%Patch availableApr 25, 2026

Auth bypass in Clerk JS routes; bypasses middleware gating.

common questions

Is CVE-2026-41248 being exploited?

Not confirmed. CVE-2026-41248 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-41248?

CVE-2026-41248 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-41248?

Yes. A fix has been recorded for CVE-2026-41248. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-41248 affect?

CVE-2026-41248 affects @clerk/nextjs, @clerk/nuxt, @clerk/astro, @clerk/shared. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-41248?

Upgrade to fixed Clerk packages (see versions above).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@clerk/nextjs@clerk/nuxt@clerk/astro@clerk/shared
impact

Attacker can bypass auth gating and reach downstream handlers; unauthorized actions possible.

action required

Patch when possible

affected versions
clerk astro
  • affected>= 0.0.1 and < 1.5.7
  • affected>= 2.0.0-snapshot.v20241206174604 and <= 2.17.9
  • affected>= 3.0.0 and < 3.0.15
clerk nextjs
  • affected>= 5.0.0 and < 5.7.6
  • affected>= 6.0.0-snapshot.vb87a27f and < 6.39.2
  • affected>= 7.0.0 and < 7.2.1
clerk nuxt
  • affected>= 1.1.0 and < 1.13.28
  • affected>= 2.0.0 and < 2.2.2
clerk shared
  • affected>= 2.20.17 and < 2.22.1
  • affected>= 3.0.0-canary.v20250225091530 and < 3.47.4
  • affected>= 4.0.0 and < 4.8.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free