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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EPSS
15.7%
KEV
Not listed

Published

May 11, 2026

Last Modified

June 1, 2026

Advisory Details (1)

Auto-updated May 11, 2026
Patch available. Sources: github.
github Patch Available

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 rangeFixed inDependents
@clerk/astro—3.0.18—
@clerk/backend—3.2.14—
@clerk/chrome-extension—3.1.15—
@clerk/clerk-expo—2.19.36—
@clerk/clerk-js—6.7.5—
@clerk/clerk-react—5.61.6—
@clerk/expo—3.2.2—
@clerk/express—2.1.6—
@clerk/fastify—3.1.16—
@clerk/hono—0.1.16—
@clerk/nextjs—7.2.4—
@clerk/nuxt—2.2.5—
@clerk/react—6.4.3—
@clerk/react-router—3.1.4—
@clerk/shared—4.8.3—
@clerk/tanstack-react-start—1.1.4—
@clerk/vue—2.0.16—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 104 total refreshes for this CVE.

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

Related CVEs(same CWE)

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 in the National Vulnerability Database 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 15.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42349, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs