pbkdf2 (npm) has 3 known vulnerabilities, the worst rated CRITICAL. Upgrade to 3.1.7 or later to clear all of them. No malicious-package signal is recorded.
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for pbkdf2 (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does pbkdf2 have known vulnerabilities?
Yes. CyberXYZ records 3 known vulnerabilities for pbkdf2 (npm), the worst rated CRITICAL. They are GHSA-v62p-rq8g-8h59, GHSA-h7cp-r72f-jxh6, GHSA-477h-4r7f-fvrx.
Which version of pbkdf2 should I use?
3.1.7 or later clears every advisory recorded for pbkdf2 (npm). Check the release you pick before installing it.
How do I check pbkdf2 before installing?
Search pbkdf2 in CyberXYZ Check at https://cyberxyz.io/check?q=pbkdf2. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:24 UTC. The most recent advisory here was published 2026-10-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.