@clerk/express (npm) has 3 known vulnerabilities, the worst rated HIGH. Upgrade to 2.1.6 or later to clear all of them. No malicious-package signal is recorded.
has(), auth.protect(), and related authorization predicates in @clerk/shared, @clerk/nextjs, @clerk/backend, and other framework SDKs can return true for…
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for @clerk/express (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @clerk/express have known vulnerabilities?
Yes. CyberXYZ records 3 known vulnerabilities for @clerk/express (npm), the worst rated HIGH. They are GHSA-w24r-5266-9c3c, GHSA-gjxx-92w9-8v8f, GHSA-9mp4-77wg-rwx9.
Which version of @clerk/express should I use?
2.1.6 or later clears every advisory recorded for @clerk/express (npm). Check the release you pick before installing it.
How do I check @clerk/express before installing?
Search @clerk/express in CyberXYZ Check at https://cyberxyz.io/check?q=%40clerk%2Fexpress. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:13 UTC. The most recent advisory here was published 2026-04-30. Updated continuously from NVD, GHSA, OSV and CNA feeds.