VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@clerk/shared: vulnerability history, versions and safety

@clerk/shared is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 30 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @clerk/shared vulnerabilities

Vulert verdict on @clerk/shared 4.41.0 i

Updated on 23 Oct 2026

Good news: 4.41.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 4.41.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.41.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.41.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 30 Apr 2026 i
  • Highest CVSS 7.6 i
  • With no published fix 0 i
  • Depended on by 142 packages i
  • Stars 1,767 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @clerk/shared, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.41.1-canary.v20261022224248 22 Oct 2026 none MIT — Details →
4.41.1-canary.v20261022215346 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022213945 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022211328 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022205601 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022204041 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022203208 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022202440 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022200952 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022200312 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022193344 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022184837 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022183301 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022183939 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022180655 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022173924 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022172519 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022162651 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022152038 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022150853 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022134015 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022133215 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022063025 22 Oct 2026 none MIT — Details →
4.42.0-canary.v20261022005720 22 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021234820 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021233524 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021233003 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021232213 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021222124 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021200659 21 Oct 2026 none MIT — Details →
4.42.0-snapshot.v20261021181323 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021175912 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021170419 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021164018 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021162612 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021154525 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021151234 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021142648 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021111350 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021033948 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261021001622 21 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020231808 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020225711 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020222531 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020204615 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020191927 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020190010 20 Oct 2026 none MIT — Details →
4.41.0 20 Oct 2026 none MIT — Details →
4.41.1-canary.v20261020180710 20 Oct 2026 none MIT — Details →
4.41.0-canary.v20261020174755 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020162624 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020154230 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020152305 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020144641 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020144206 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020042935 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261020003732 20 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019212020 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019210128 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019201417 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019200628 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019192629 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019185654 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019184425 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019180214 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019172604 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261019134656 19 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016220137 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016210732 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016203220 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016195242 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016193000 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016185259 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016183203 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016181755 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016175446 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016174759 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016173544 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016172349 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016164649 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016162739 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016154159 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016151750 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016145416 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261016101811 16 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015203451 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015201124 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015194219 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015191837 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015190205 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015183833 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015180401 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015174419 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015173035 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015171615 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015163134 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015161436 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015154402 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261015024336 15 Oct 2026 none MIT — Details →
4.40.1-canary.v20261014222956 14 Oct 2026 none MIT — Details →
4.40.1-canary.v20261014212511 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014203001 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014201437 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014191520 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014190113 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014185054 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014182813 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014175017 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014174506 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014170407 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014145931 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014143209 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014003907 14 Oct 2026 none — — Details →
4.40.1-canary.v20261014002655 14 Oct 2026 none — — Details →
4.40.1-canary.v20261013212237 13 Oct 2026 none — — Details →
4.40.1-canary.v20261013200714 13 Oct 2026 none — — Details →
4.40.1-canary.v20261013191718 13 Oct 2026 none — — Details →
4.40.1-canary.v20261013190811 13 Oct 2026 none — — Details →
4.40.1-canary.v20261013190243 13 Oct 2026 none — — Details →
4.40.1-canary.v20261013183350 13 Oct 2026 none — — Details →

The newest 120 of 5,776 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @clerk/shared

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-42349: Clerk Package Authorization Bypass Vulnerability 7.6 high 3.47.5 30 Apr 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @clerk/shared

Is @clerk/shared safe to use?

Vulert records 1 vulnerabilities for @clerk/shared in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @clerk/shared's Vulert package health score?

Vulert scores @clerk/shared 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @clerk/shared affected?

No. 4.41.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @clerk/shared have?

1 vulnerability is recorded for @clerk/shared in the npm ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @clerk/shared vulnerabilities disclosed?

1 vulnerability was recorded for @clerk/shared in the last 12 months, and the oldest entry in this database dates to 30 Apr 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @clerk/shared are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @clerk/shared for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @clerk/shared version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.