clerk javascript up to 1.5.6/2.17.9/3.0.14 interpretation conflict
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in clerk javascript up to 1.5.6/2.17.9/3.0.14. This vulnerability affects unknown code. Performing a manipulation results in interpretation conflict. This vulnerability is identified as CVE-2026-41248. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in clerk javascript up to 1.5.6/2.17.9/3.0.14. This affects some unknown functionality. The manipulation with an unknown input leads to a interpretation conflict vulnerability. CWE is classifying the issue as CWE-436. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Clerk JavaScript is the official JavaScript repository for Clerk authentication. createRouteMatcher in @clerk/nextjs, @clerk/nuxt, and @clerk/astro can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers. This vulnerability is fixed in @clerk/astro 1.5.7, 2.17.10, and 3.0.15; @clerk/nextjs 5.7.6, 6.39.2, and 7.2.1; @clerk/nuxt 1.13.28 and 2.2.2; and @clerk/shared 2.22.1, 3.47.4, anc 4.8.1
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-41248 since 04/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.5.7 or 3.0.15 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25632). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 1.5.0
- 1.5.1
- 1.5.2
- 1.5.3
- 1.5.4
- 1.5.5
- 1.5.6
- 2.17.0
- 2.17.1
- 2.17.2
- 2.17.3
- 2.17.4
- 2.17.5
- 2.17.6
- 2.17.7
- 2.17.8
- 2.17.9
- 3.0.0
- 3.0.1
- 3.0.2
- 3.0.3
- 3.0.4
- 3.0.5
- 3.0.6
- 3.0.7
- 3.0.8
- 3.0.9
- 3.0.10
- 3.0.11
- 3.0.12
- 3.0.13
- 3.0.14
Website
- Product: https://github.com/clerk/javascript/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Interpretation conflictCWE: CWE-436
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: javascript 1.5.7/3.0.15
Timeline
04/18/2026 CVE reserved04/25/2026 Advisory disclosed
04/25/2026 VulDB entry created
04/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-vqx2-fgx2-5wq9
Status: Confirmed
CVE: CVE-2026-41248 (🔒)
GCVE (CVE): GCVE-0-2026-41248
GCVE (VulDB): GCVE-100-359571
EUVD: 🔒
Entry
Created: 04/25/2026 04:53Updated: 04/25/2026 23:53
Changes: 04/25/2026 04:53 (64), 04/25/2026 23:53 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.