npm package
crypto-js 3.1.8 vulnerabilities, and the version that fixes all of them
crypto-js 3.1.8 has 2 known vulnerabilities (2 rated high or critical); 4.2.0 fixes all of them. 4.2.0 is a deprecated release. The maintainers have deprecated crypto-js.
npm (opens in a new tab) describes it as “JavaScript library of crypto standards.”
- Known vulnerabilities
- 2
- 2 rated high or critical
- Released
- Oct 27, 2016
- Latest is 4.2.0
- Downloads last week
- 45.5K
- Under 1% of crypto-js downloads
- Licence
- MIT
- Dependencies
- None
- Resolved by deps.dev
- Status
- Package deprecated
What to upgrade to
Every newer release we checked still has known vulnerabilities. The fewer, the better.
Newest 3.x release. Released Feb 12, 2020.
2 known vulnerabilities, worst rated warningDeprecatedFixes all 2 known vulnerabilities and the latest release. Released Oct 24, 2023.
Deprecated release
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- CriticalVulnerability
2 known vulnerabilities in crypto-js 3.1.8
EPSS: top 51%2 rated high or critical. Most serious: CVE-2023-46233, crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard. Upgrading to 4.2.0 fixes all of them.
- WarningMaintenance
crypto-js is deprecated on npm
The maintainers' deprecation notice: "Active development of CryptoJS has been discontinued. This library is no longer maintained."
- LowOutdated
crypto-js 3.1.8 is 1 major version behind
Latest release is 4.2.0.
- LowOpenSSF Scorecard
brix/crypto-js scores 2.2/10 on OpenSSF Scorecard
Weakest checks: Not actively maintained (Maintained 0/10); No branch protection (Branch-Protection 0/10); No security policy (Security-Policy 0/10). A low score means weaker upstream security practices, not a known vulnerability.
Every advisory for crypto-js 3.1.8
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
CriticalCVE-2023-46233 on OSV.dev (opens in a new tab)GHSA-xwcq-pm8m-c4vfEPSS: top 51%
crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
Fixed in 4.2.0. Published Oct 25, 2023.
CriticalCVE-2026-71851 on OSV.dev (opens in a new tab)GHSA-rg76-677x-56q9EPSS: top 56%
crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency Chain
Fixed in 4.0.0. Published Aug 7, 2026.
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.
Is crypto-js the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly crypto-js 3.1.8, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.