Versions of secure-compare prior to 3.0.1 are affected by a vulnerability that results in the package always returning true when comparing two strings of the…
Full advisory text at GitHub advisory or NVD.
npm package report
Is secure-compare safe?
secure-compare (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 3.0.1 or later to clear it. No malicious-package signal is recorded.
// reach
0 direct dependencies
none carry a known advisory
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.5
high
severity band, no base score published
epss
1.4%
medium
chance of exploitation in 30 days, 74th percentile of all CVEs
xyz score
4.1
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-h9x2-5rm7-x4gm, the advisory selected below
// 1 advisories
Is secure-compare safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for secure-compare (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does secure-compare have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for secure-compare (npm), the worst rated HIGH. They are GHSA-h9x2-5rm7-x4gm.
Which version of secure-compare should I use?
3.0.1 or later clears every advisory recorded for secure-compare (npm). Check the release you pick before installing it.
How do I check secure-compare before installing?
Search secure-compare in CyberXYZ Check at https://cyberxyz.io/check?q=secure-compare. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:04 UTC. The most recent advisory here was published 2019-06-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.