CVE-2026-42349

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

Published

May 11, 2026

Last Modified

June 1, 2026

Advisory Details (1)

Auto-updated May 11, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Authorization bypass when combining organization, billing, or reverification checks · Advisory · clerk/javascript · GitHub

https://github.com/clerk/javascript/security/advisories/GHSA-w24r-5266-9c3c

Vendor Advisories for CVE-2026-42349(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(17 across 1 ecosystem)
npm(17)
PackageVulnerable rangeFix by version rangeDependents
@clerk/astro—
  • 2.0.0 up to 2.17.11: fixed in 2.17.11
  • 3.0.0 up to 3.0.18: fixed in 3.0.18
—
@clerk/backend—
  • 2.0.0 up to 2.33.3: fixed in 2.33.3
  • 3.0.0 up to 3.2.14: fixed in 3.2.14
—
@clerk/chrome-extension—
  • 1.3.5 up to 2.9.15: fixed in 2.9.15
  • 3.0.0 up to 3.1.15: fixed in 3.1.15
—
@clerk/clerk-expo—
  • 2.2.11 up to 2.19.36: fixed in 2.19.36
—
@clerk/clerk-js—
  • 5.22.0 up to 5.125.10: fixed in 5.125.10
  • 6.0.0 up to 6.7.5: fixed in 6.7.5
—
@clerk/clerk-react—
  • 5.9.0 up to 5.61.6: fixed in 5.61.6
—
@clerk/expo—
  • 3.0.0 up to 3.2.2: fixed in 3.2.2
—
@clerk/express—
  • 0.1.0 up to 1.7.79: fixed in 1.7.79
  • 2.0.0 up to 2.1.6: fixed in 2.1.6
—
@clerk/fastify—
  • 1.0.42 up to 2.6.31: fixed in 2.6.31
  • 3.0.0 up to 3.1.16: fixed in 3.1.16
—
@clerk/hono—
  • 0.0.2 up to 0.1.16: fixed in 0.1.16
—
@clerk/nextjs—
  • 6.0.0 up to 6.39.3: fixed in 6.39.3
  • 7.0.0 up to 7.2.4: fixed in 7.2.4
—
@clerk/nuxt—
  • 1.0.0 up to 1.13.29: fixed in 1.13.29
  • 2.0.0 up to 2.2.5: fixed in 2.2.5
—
@clerk/react—
  • 6.0.0 up to 6.4.3: fixed in 6.4.3
—
@clerk/react-router—
  • 0.0.1 up to 2.4.13: fixed in 2.4.13
  • 3.0.0 up to 3.1.4: fixed in 3.1.4
—
@clerk/shared—
  • 3.0.0 up to 3.47.5: fixed in 3.47.5
  • 4.0.0 up to 4.8.3: fixed in 4.8.3
—
@clerk/tanstack-react-start—
  • 0.0.1 up to 0.29.11: fixed in 0.29.11
  • 1.0.0 up to 1.1.4: fixed in 1.1.4
—
@clerk/vue—
  • 1.0.0 up to 1.17.21: fixed in 1.17.21
  • 2.0.0 up to 2.0.16: fixed in 2.0.16
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 166 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 06:58 UTCOSV refresh
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 19:31 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-12 15:01 UTCEPSS rescore
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 12:23 UTCOSV refresh
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-08 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-23 18:39 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 11:11 UTCEG score recompute
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:26 UTCEG score recompute
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 02:58 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-12 16:31 UTCEG score recompute
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-11 15:47 UTCEG score recompute
  29. 2026-08-11 13:43 UTCEPSS rescore
  30. 2026-08-11 01:11 UTCEG score recompute
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-09 15:00 UTCEG score recompute
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 02:15 UTCEG score recompute
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-08 03:07 UTCEG score recompute
  37. 2026-08-05 21:58 UTCEG score recompute
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:38 UTCEPSS rescore
  41. 2026-08-03 19:26 UTCEG score recompute
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 14:54 UTCEG score recompute
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-02 02:09 UTCEG score recompute
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-27 14:13 UTCEPSS rescore
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-25 14:18 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:11 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 14:31 UTCEPSS rescore
  61. 2026-07-19 02:29 UTCEPSS rescore
  62. 2026-07-18 10:04 UTCEPSS rescore
  63. 2026-07-16 17:03 UTCEPSS rescore
  64. 2026-07-16 03:23 UTCOSV refresh
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-13 22:30 UTCEPSS rescore
  68. 2026-07-13 06:13 UTCEPSS rescore
  69. 2026-07-12 05:46 UTCEPSS rescore
  70. 2026-07-11 08:27 UTCEPSS rescore
  71. 2026-07-09 19:10 UTCEPSS rescore
  72. 2026-07-08 15:15 UTCEPSS rescore
  73. 2026-07-07 13:46 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-06 16:27 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

4 shown

npm:@clerk/react-router · npm:@clerk/hono · npm:@clerk/shared

Frequently asked(5)

What is CVE-2026-42349?
CVE-2026-42349 is a high vulnerability published on May 11, 2026. 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…
When was CVE-2026-42349 disclosed?
CVE-2026-42349 was first published on May 11, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42349 actively exploited?
CVE-2026-42349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42349?
CVE-2026-42349 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-42349?
A fix for CVE-2026-42349 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42349 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42349

Explore →

Is Your Infrastructure Affected by CVE-2026-42349?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs