npm package report

Is @clerk/backend safe?

@clerk/backend (npm) has 3 known vulnerabilities, the worst rated HIGH. Upgrade to 3.2.14 or later to clear all of them. No malicious-package signal is recorded.

// reach

3 direct dependencies

1 carry known advisories, worst CRITICAL

@clerk/sharedCRITICAL

6 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

cvss

7.6

high

CVSS v4.0 base score out of 10

epss

0.25%

low

chance of exploitation in 30 days, 16th percentile of all CVEs

xyz score

4.0

medium

CyberXYZ composite out of 10

fig. 01 — GHSA-w24r-5266-9c3c, the advisory selected below

// 3 advisories

GHSA-w24r-5266-9c3c

HIGHGitHub ratingCVE-2026-42349

has(), auth.protect(), and related authorization predicates in @clerk/shared, @clerk/nextjs, @clerk/backend, and other framework SDKs can return true for…

Full advisory text at GitHub advisory or NVD.

// cvss v4.0 vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: Present
Privileges required: Low
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): High
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

// questions

Is @clerk/backend safe to install?

CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for @clerk/backend (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.

Does @clerk/backend have known vulnerabilities?

Yes. CyberXYZ records 3 known vulnerabilities for @clerk/backend (npm), the worst rated HIGH. They are GHSA-w24r-5266-9c3c, GHSA-gjxx-92w9-8v8f, GHSA-9mp4-77wg-rwx9.

Which version of @clerk/backend should I use?

3.2.14 or later clears every advisory recorded for @clerk/backend (npm). Check the release you pick before installing it.

How do I check @clerk/backend before installing?

Search @clerk/backend in CyberXYZ Check at https://cyberxyz.io/check?q=%40clerk%2Fbackend. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.

Checked 2026-11-14 at 06:31 UTC. The most recent advisory here was published 2026-04-30. Updated continuously from NVD, GHSA, OSV and CNA feeds.