Home/CVE/Clerk JavaScript is the official JavaScript repository for Clerk authentication. has(), auth.protect(), and related auth
CVE
CVE-2026-42349
Clerk JavaScript is the official JavaScript repository for Clerk authentication. has(), auth.protect(), and related auth
Clerk JavaScript is the official JavaScript repository for Clerk authentication. has(), auth.protect(), and related authorization predicates in @clerk/shared, @clerk/nextjs, @clerk/backend, and other framework SDKs can return true for certain combined authorization checks when the result should be false, allowing a gated action to proceed for a user who does not satisfy the full set of requested conditions. This call shape can be bypassed if certain conditions are met: a has() or auth.protect() call that combines a reverification check with any of role, permission, feature, or plan, or that combines a billing check (feature or plan) with a role or permission check. This vulnerability is fixed in @clerk/clerk-js 5.125.10 and 6.7.5.
HIGH · CVSS 8.1
EPSS 0.00056
Schedule remediation
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-42349, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
▤
Affected Products & Versions
29clerk clerk\/astro>= 2.0.0 and < 2.17.11
clerk clerk\/astro>= 3.0.0 and < 3.0.18
clerk clerk\/backend>= 2.0.0 and < 2.33.3
clerk clerk\/backend>= 3.0.0 and < 3.2.14
clerk clerk\/chrome-extension>= 1.3.5 and < 2.9.15
clerk clerk\/chrome-extension>= 3.0.0 and < 3.1.15
clerk clerk\/clerk-expo>= 2.2.11 and < 2.19.36
clerk clerk\/clerk-js>= 5.22.0 and < 5.125.10
▤
Affected Packages
17Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
npm
@clerk/astro
HIGH
fixed in 2.17.11
npm
@clerk/backend
HIGH
fixed in 2.33.3
npm
@clerk/chrome-extension
HIGH
fixed in 2.9.15
npm
@clerk/clerk-expo
HIGH
fixed in 2.19.36
npm
@clerk/clerk-js
HIGH
fixed in 5.125.10
npm
@clerk/clerk-react
HIGH
fixed in 5.61.6
npm
@clerk/expo
HIGH
fixed in 3.2.2
npm
@clerk/express
HIGH
fixed in 1.7.79
npm
@clerk/fastify
HIGH
fixed in 2.6.31
npm
@clerk/hono
HIGH
fixed in 0.1.16
npm
@clerk/nextjs
HIGH
fixed in 6.39.3
npm
@clerk/nuxt
HIGH
fixed in 1.13.29
npm
@clerk/react
HIGH
fixed in 6.4.3
npm
@clerk/react-router
HIGH
fixed in 2.4.13
npm
@clerk/shared
HIGH
fixed in 3.47.5
npm
@clerk/tanstack-react-start
HIGH
fixed in 0.29.11
npm
@clerk/vue
HIGH
fixed in 1.17.21
▣
Scoring & Timeline
8.1
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
no
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/clerk/javascript/security/advisories/GHSA-w24r-5266-9c3cMitigationVendor Advisory