crypto-js vulnerabilities

JavaScript library of crypto standards.

Registry
npm
Latest
4.2.0
License
MIT
Source
github.com/brix/crypto-js (opens the source repository in a new tab)

3 known advisories

The latest version, 4.2.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install crypto-js@4.2.0

Security advisories for crypto-js

  • CriticalGHSA-rg76-677x-56q97 Aug 2026

    crypto-js: Insufficient Entropy in Cryptographic Secret Generation via Vulnerable CryptoJS Dependency Chain

    Affected
    <4.0.0
    Fixed in
    4.0.0
  • CriticalGHSA-xwcq-pm8m-c4vf25 Oct 2023

    crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard

    Affected
    <4.2.0
    Fixed in
    4.2.0
  • MediumGHSA-3w3w-pxmm-2w2j12 Jun 2023

    crypto-js uses insecure random numbers

    Affected
    >=3.2.0 <3.2.1
    Fixed in
    3.2.1

Which of your client projects still run an old crypto-js?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.