crypto-js (npm) has 3 known vulnerabilities, the worst rated CRITICAL. Upgrade to 4.2.0 or later to clear all of them. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 46th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-rg76-677x-56q9, the advisory selected below
CryptoJS.lib.WordArray.random() in affected versions is not a cryptographically secure random number generator.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for crypto-js (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 3 known vulnerabilities for crypto-js (npm), the worst rated CRITICAL. They are GHSA-rg76-677x-56q9, GHSA-xwcq-pm8m-c4vf, GHSA-3w3w-pxmm-2w2j.
4.2.0 or later clears every advisory recorded for crypto-js (npm). Check the release you pick before installing it.
Search crypto-js in CyberXYZ Check at https://cyberxyz.io/check?q=crypto-js. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 02:03 UTC. The most recent advisory here was published 2026-08-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.