● npm package
crypto-js
Crypto-js has three security advisories. The newest release any of them names as the fix is 4.2.0.
As of , crypto-js has three security advisories. The newest release any of them names as the fix is 4.2.0.
Your version, and the version to upgrade to
| If you run | Upgrade to | Advisories |
|---|---|---|
| Before 4.2.0 | 4.2.0 | 3 advisories |
Security advisories, newest first
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| CVE-2026-71851GHSA-rg76-677x-56q9 | crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency ChainCritical severity | Before 4.0.0 | 4.0.0 | |
| CVE-2023-46233GHSA-xwcq-pm8m-c4vf | crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standardCritical severity | Before 4.2.0 | 4.2.0 | |
| CVE-2020-36732GHSA-3w3w-pxmm-2w2j | crypto-js uses insecure random numbersModerate severity | From 3.2.0 before 3.2.1 | 3.2.1 |
Other npm packages
- connect3 advisories
- content3 advisories
- cyberchef3 advisories
- decode-uri-component3 advisories
Sources
- Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0