@clerk/react-router (npm) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 3.1.4 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…
// questionsIs @clerk/react-router safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for @clerk/react-router (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @clerk/react-router have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for @clerk/react-router (npm), the worst rated HIGH. They are GHSA-w24r-5266-9c3c, GHSA-9mp4-77wg-rwx9.
Which version of @clerk/react-router should I use?
3.1.4 or later clears every advisory recorded for @clerk/react-router (npm). Check the release you pick before installing it.
How do I check @clerk/react-router before installing?
Search @clerk/react-router in CyberXYZ Check at https://cyberxyz.io/check?q=%40clerk%2Freact-router. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:02 UTC. The most recent advisory here was published 2026-04-30. Updated continuously from NVD, GHSA, OSV and CNA feeds.