VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pbkdf2: vulnerability history, versions and safety

pbkdf2 is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 26 releases, from Jun 2025 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 06 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pbkdf2 vulnerabilities

Vulert verdict on pbkdf2 3.1.7 i

Updated on 23 Oct 2026

Good news: 3.1.7, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 3.1.7 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.7 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 1 in the last year i
  • Latest disclosure 06 Oct 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 108,079 packages i
  • Stars 203 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for pbkdf2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.7 29 Sep 2026 none MIT — Details →
3.1.6 26 May 2026 M1 MIT Yes Details →
3.1.5 24 Sep 2025 M1 MIT Yes Details →
3.1.4 23 Sep 2025 M1 MIT Yes Details →
3.1.3 20 Jun 2025 M1 MIT Yes Details →
3.1.2 09 Apr 2021 C2 M1 MIT Yes Details →
3.1.1 04 Jun 2020 C2 M1 MIT Yes Details →
3.1.0 03 Jun 2020 C2 M1 MIT Yes Details →
3.0.17 25 Sep 2018 C2 M1 MIT Yes Details →
3.0.16 20 Apr 2018 C2 M1 MIT Yes Details →
3.0.14 08 Sep 2017 C2 M1 MIT Yes Details →
3.0.13 02 Aug 2017 C2 M1 MIT Yes Details →
3.0.12 11 May 2017 C2 M1 MIT Yes Details →
3.0.11 11 May 2017 C2 M1 MIT Yes Details →
3.0.10 11 May 2017 C2 M1 MIT Yes Details →
3.0.9 05 Oct 2016 C1 M1 MIT Yes Details →
3.0.8 21 Sep 2016 C1 M1 MIT Yes Details →
3.0.7 16 Sep 2016 C1 M1 MIT Yes Details →
3.0.6 13 Sep 2016 C1 M1 MIT Yes Details →
3.0.5 12 Sep 2016 C1 M1 MIT Yes Details →
3.0.4 27 Mar 2015 C1 M1 MIT Yes Details →
3.0.3 15 Feb 2015 C1 M1 MIT Yes Details →
0.0.5 24 Apr 2014 C1 M1 MIT Yes Details →
0.0.4 18 Apr 2014 C1 M1 MIT Yes Details →
0.0.3 13 Feb 2014 C1 M1 MIT Yes Details →
0.0.2 05 Feb 2014 C1 M1 MIT Yes Details →
0.0.1 03 Feb 2014 C1 M1 MIT Yes Details →

All 27 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pbkdf2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-6545: pbkdf2 Predictable Output for Unsupported and Non-Normalized Algorithms 9.1 critical 3.1.3 23 Jun 2025
CVE-2025-6547: pbkdf2 Package Vulnerability Leading to Static Key Generation 9.1 critical 3.1.3 23 Jun 2025
CVE-2026-102414: pbkdf2 Denial of Service Vulnerability Due to Long Password Rehashing 3.7 medium 3.1.7 06 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pbkdf2

Is pbkdf2 safe to use?

Vulert records 3 vulnerabilities for pbkdf2 in npm: 2 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pbkdf2's Vulert package health score?

Vulert scores pbkdf2 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of pbkdf2 affected?

No. 3.1.7, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of pbkdf2 should I use?

3.1.7 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does pbkdf2 have?

3 vulnerabilities are recorded for pbkdf2 in the npm ecosystem: 2 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pbkdf2 vulnerabilities disclosed?

1 vulnerability was recorded for pbkdf2 in the last 12 months, and the oldest entry in this database dates to 23 Jun 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pbkdf2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pbkdf2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pbkdf2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.