npmWorst: Critical3 advisories

crypto-js: known vulnerabilities

crypto-js has 3 reviewed security advisories in the GitHub Advisory Database — 2 critical, 1 moderate. The most recent was published 2026-08-07. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the crypto-js versions running across your servers, containers and images, and ranks what to patch first.

How to fix crypto-js

Upgrade crypto-js to a release at or above the fixed version shown for each advisory below. For npm:

npm install crypto-js@4.0.0 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (3)

crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency Chain Critical 9.0 CWE-331 CWE-334 CWE-338 — Affected: before 4.0.0. Fixed in 4.0.0. Published 2026-08-07. GHSA-rg76-677x-56q9 · CVE-2026-71851
crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard Critical 9.1 CWE-327 CWE-328 CWE-916 — Affected: before 4.2.0. Fixed in 4.2.0. Published 2023-10-25. GHSA-xwcq-pm8m-c4vf · CVE-2023-46233
crypto-js uses insecure random numbers Moderate 5.3 CWE-330 CWE-331 — Affected: from 3.2.0 up to 3.2.1. Fixed in 3.2.1. Published 2023-06-12. GHSA-3w3w-pxmm-2w2j · CVE-2020-36732

Find crypto-js across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.