npm package
crypto-js vulnerabilities by version
The latest release, 4.2.0 (Oct 24, 2023), has no known vulnerabilities. 8% of last week’s 19.2M downloads went to versions with known vulnerabilities. OSV.dev lists 3 advisories for crypto-js; the newest was published on Aug 7, 2026. The maintainers have deprecated crypto-js.
npm (opens in a new tab) describes it as “JavaScript library of crypto standards.”
- Latest release
- 4.2.0
- Oct 24, 2023, no known vulnerabilities
- Downloads last week
- 19.2M
- All versions, from npm
- Advisories on OSV.dev
- 3
- Newest Aug 7, 2026
- Licence
- MIT
- Status
- Deprecated
- Active development of CryptoJS has been discontinued. This library is no longer maintained.
Most-downloaded versions last week
From npm’s per-version download counts for the last 7 days, each checked against OSV.dev. Open a version for its advisories and what to upgrade to.
Who is still on a vulnerable crypto-js
8% of last week’s 19.2M crypto-js downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Release lines
The newest release of each major line, from the registry. crypto-js doesn’t publish support dates we can check.
Newest advisories
The 3 most recently published, with the versions each one affects.
CriticalCVE-2026-71851 on OSV.dev (opens in a new tab)GHSA-rg76-677x-56q9
crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency Chain
Affects < 4.0.0. Published Aug 7, 2026.
CriticalCVE-2023-46233 on OSV.dev (opens in a new tab)GHSA-xwcq-pm8m-c4vf
crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
Affects < 4.2.0. Published Oct 25, 2023.
WarningCVE-2020-36732 on OSV.dev (opens in a new tab)GHSA-3w3w-pxmm-2w2j
crypto-js uses insecure random numbers
Affects >= 3.2.0, < 3.2.1. Published Jun 12, 2023.
Which crypto-js do you have?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task for your coding agent. Free, no sign-up.
How this page is checked
StackPrism reads every OSV.dev advisory for crypto-js, merges duplicates filed under several ids, and asks OSV.dev which ones affect each version listed. Releases and their dates come from deps.dev, downloads from npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.