pbkdf2 silently returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos supported by Node.js
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-6545
PublishedImproper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js. This issue affects pbkdf2: from 3.0.10 through 3.1.2.
- Source published
- 23 Jun 2025 18:41:18 UTC
- Source modified
- 23 Jun 2025 19:26:40 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H
euvd · EUVD-2025-18922
PublishedImproper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js. This issue affects pbkdf2: from 3.0.10 through 3.1.2.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jun 23, 2025, 6:41:18 PM
dateUpdated: Jun 23, 2025, 7:26:40 PM
11 related source bulletins · separate from aliases
SUSE-SU-2025:3744-1: Security update for aws-cli, local-npm-registry, python-boto3, python-botocore, python-coverage, python-flaky, python-pluggy, python-pytest, python-pytest-cov, python-pytest-html, python-pytest-metadata, python-pytest-mock
CVE-2024-21538 · CVE-2024-48948 · CVE-2024-48949 · CVE-2025-5889 · CVE-2025-6545 · CVE-2025-6547
WID-SEC-W-2025-1409: IBM App Connect Enterprise: Mehrere Schwachstellen ermöglichen Manipulation von Daten
CVE-2025-6545 · CVE-2025-6547
RHSA-2025:22905: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.19.4
CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-64756
RHSA-2026:3710: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.3
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
RHSA-2025:10738: Red Hat Security Advisory: Kiali 2.4.7 for Red Hat OpenShift Service Mesh 3.0
CVE-2025-6545 · CVE-2025-6547
RHSA-2025:14474: Red Hat Security Advisory: RHTAS 1.2.1- Red Hat Trusted Artifact Signer Release
CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9288
RHSA-2026:3712: Red Hat Security Advisory: Red Hat OpenShift Pipelines Release 1.15.4
CVE-2024-37890 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-66031 · CVE-2025-66506 · CVE-2025-66564
openSUSE-SU-2026:11126-1: velociraptor-0.7.0.4.git185.a5708584-2.1 on GA media
CVE-2023-45288 · CVE-2024-45339 · CVE-2025-13465 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-24358 · CVE-2025-47911 · CVE-2025-58058 · CVE-2025-58181 · CVE-2025-58190 · CVE-2025-5889 · CVE-2025-64718 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-7783 · CVE-2026-1229 · CVE-2026-25128 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-26278 · CVE-2026-26996 · CVE-2026-27136 · CVE-2026-2739 · CVE-2026-27606 · CVE-2026-27904 · CVE-2026-33036 · CVE-2026-33186 · CVE-2026-33487 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-42039 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
RHSA-2025:14090: Red Hat Security Advisory: Red Hat Developer Hub 1.7.0 release.
CVE-2025-5417 · CVE-2025-6545 · CVE-2025-7338 · CVE-2025-22870 · CVE-2025-32996 · CVE-2025-32997 · CVE-2025-48387 · CVE-2025-48997 · CVE-2025-54419
WID-SEC-W-2026-2933: Splunk SOAR: Mehrere Schwachstellen
CVE-2025-13465 · CVE-2025-13473 · CVE-2025-14550 · CVE-2025-15599 · CVE-2025-53859 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-66221 · CVE-2025-67724 · CVE-2025-67725 · CVE-2025-67726 · CVE-2025-68428 · CVE-2025-69873 · CVE-2026-0540 · CVE-2026-1207 · CVE-2026-1285 · CVE-2026-1287 · CVE-2026-1312 · CVE-2026-1642 · CVE-2026-2004 · CVE-2026-2005 · CVE-2026-2006 · CVE-2026-21226 · CVE-2026-21860 · CVE-2026-22702 · CVE-2026-22815 · CVE-2026-2391 · CVE-2026-24001 · CVE-2026-24040 · CVE-2026-24043 · CVE-2026-24133 · CVE-2026-24737 · CVE-2026-25535 · CVE-2026-25673 · CVE-2026-25674 · CVE-2026-25755 · CVE-2026-25940 · CVE-2026-26007 · CVE-2026-26996 · CVE-2026-27199 · CVE-2026-2739 · CVE-2026-27651 · CVE-2026-27654 · CVE-2026-27784 · CVE-2026-27959 · CVE-2026-28277 · CVE-2026-28684 · CVE-2026-28753 · CVE-2026-28755 · CVE-2026-29063 · CVE-2026-2950 · CVE-2026-30922 · CVE-2026-31898 · CVE-2026-31938 · CVE-2026-31958 · CVE-2026-32141 · CVE-2026-32597 · CVE-2026-32647 · CVE-2026-33228 · CVE-2026-33532 · CVE-2026-33671 · CVE-2026-33672 · CVE-2026-33750 · CVE-2026-34513 · CVE-2026-34514 · CVE-2026-34515 · CVE-2026-34516 · CVE-2026-34517 · CVE-2026-34518 · CVE-2026-34519 · CVE-2026-34520 · CVE-2026-34525 · CVE-2026-34601 · CVE-2026-35536 · CVE-2026-40087 · CVE-2026-40460 · CVE-2026-40701 · CVE-2026-41066 · CVE-2026-42215 · CVE-2026-42284 · CVE-2026-42934 · CVE-2026-42945 · CVE-2026-42946 · CVE-2026-44243 · CVE-2026-44244 · CVE-2026-4800 · CVE-2026-76356 · CVE-2026-76357 · CVE-2026-76358 · CVE-2026-76359 · CVE-2026-76360 · CVE-2026-76361 · CVE-2026-76362 · CVE-2026-76363 · CVE-2026-76364 · CVE-2026-76365 · CVE-2026-76366 · CVE-2026-76367 · CVE-2026-76368 · CVE-2026-76369 · CVE-2026-76370 · CVE-2026-9256
openSUSE-SU-2025:15280-1: python311-pytest-html-4.1.1-6.1 on GA media
CVE-2025-5889 · CVE-2025-6545
- Source published
- Jun 23, 2025, 6:41:18 PM (timezone not stated)
- Source modified
- Jun 23, 2025, 7:26:40 PM (timezone not stated)
- Saved here
- 15 Nov 2026 05:39:19 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 4.0 · 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H
nvd · CVE-2025-6545
PublishedImproper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js. This issue affects pbkdf2: from 3.0.10 through 3.1.2.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-20
Original publisher date fields
published: 2025-06-23T19:15:25.220
lastModified: 2026-06-17T10:02:07.243
- Source published
- 23 Jun 2025 19:15:25 UTC
- Source modified
- 17 Jun 2026 10:02:07 UTC
- Saved here
- 25 Oct 2026 03:17:36 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 7ffcee3d-2c14-4c3e-b844-86c6a321a158 · Secondary · 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
osv · GHSA-h7cp-r72f-jxh6
Published### Summary This affects both: 1. Unsupported algos (e.g. `sha3-256` / `sha3-512` / `sha512-256`) 2. Supported but non-normalized algos (e.g. `Sha256` / `Sha512` / `SHA1` / `sha-1` / `sha-256` / `sha-512`) All of those work correctly in Node.js, but this polyfill silently returns highly predictable ouput Under Node.js (only with `pbkdf2/browser` import, unlikely) / Bun (`pbkdf2` top-level import is affected), the memory is not zero-filled but is uninitialized, as `Buffer.allocUnsafe` is used Under browsers, it just returns zero-filled buffers (Which is also critical, those are completely unacceptable as kdf output and ruin security) ### Were you affected? The full list of arguments that were **not** affected were literal: * `'md5'` * `'sha1'` * `'sha224'` * `'sha256'` * `'sha384'` * `'sha512'` * `'rmd160'` * `'ripemd160'` Any other arguments, e.g. representation variations of the above ones like `'SHA-1'`/`'sha-256'`/`'SHA512'` or different algos like `'sha3-512'`/`'blake2b512'`, while supported on Node.js `crypto` module, returned predictable output on `pbkdf2` (or `crypto` browser/bundlers polyfill) --- Beware of packages re-exporting this under a different signature, like (abstract): ```js const crypto = require('crypto') module.exports.deriveKey = (algo, pass, salt) => crypto.pbkdf2Sync(pass, salt, 2048, 64, algo) ``` In this case, the resulting `deriveKey` method is also affected (to the same extent / conditions as listed here). ### Environments This affects `require('crypto')` in polyfilled mode (e.g. from `crypto-browserify`, `node-libs-browser`, `vite-plugin-node-polyfills`, `node-stdlib-browser`, etc. -- basically everything that bundles/polfyills `crypto` * In bundled code (e.g. Webpack / Vite / whatever), this affects `require('crypto')` and `require('pbkdf2')` * On Node.js, this does not affect `require('pbkdf2')` (or `require('crypto')` obviously), but affects `require('pbkdf2/browser')` * On Bun, this _does_ affect `require('pbkdf2')` _and_ `require('pbkdf2/browser')` (and returns uninitialized memory, often zeros / sparse flipped bytes) ### PoC ```js const node = require('crypto') const polyfill = require('pbkdf2/browser') const algos = [ 'sha3-512', 'sha3-256', 'SHA3-384', 'Sha256', 'Sha512', 'sha512-256', 'SHA1', 'sha-1', 'blake2b512', 'RMD160', 'RIPEMD-160', 'ripemd-160', ] for (const algo of algos) { for (const { pbkdf2Sync } of [node, polyfill]) { const key = pbkdf2Sync('secret', 'salt', 100000, 64, algo) console.log(`${algo}: ${key.toString('hex')}`); } } ``` Output (odd lines are Node.js, even is `pbkdf2` module / polyfill): ``` sha3-512: de00370414a3251d6d620dc8f7c371644e5d7f365ab23b116298a23fa4077b39deab802dd61714847a5c7e9981704ffe009aee5bb40f6f0103fc60f3d4cedfb0 sha3-512: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 sha3-256: 76bf06909b91e4c968700078ee36af92019d0839ab1fea2f345c6c8685074ca0179302633fbd84d22cff4f8744952b2d07edbfc9658e95d30fb4e93ee067c7c9 sha3-256: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 SHA3-384: 2b2b41b73f9b7bcd023f709ea84ba3c29a88edc311b737856ba9e74a2d9a928f233eb8cb404a9ba93c276edf6380c692140024a0bc12b75bfa38626207915e01 SHA3-384: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Sha256: 3fa094211c0cf2ed1d332ab43adc69aab469f0e0f2cae6345c81bb874eef3f9eb2c629052ec272ca49c2ee95b33e7ba6377b2317cd0dacce92c4748d3c7a45f0 Sha256: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Sha512: 3745e482c6e0ade35da10139e797157f4a5da669dad7d5da88ef87e47471cc47ed941c7ad618e827304f083f8707f12b7cfdd5f489b782f10cc269e3c08d59ae Sha512: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 sha512-256: e423f61987413121418715d0ebf64cb646042ae9a09fe4fd2c764a4f186ba28cf70823fdc2b03dda67a0d977c6f0a0612e5ed74a11e6f32b033cb658fa9f270d sha512-256: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 SHA1: 0e24bc5a548b236e3eb3b22317ef805664a88747c725cd35bfb0db0e4ae5539e3ed5cd5ba8c0ac018deb6518059788c8fffbe624f614fbbe62ba6a6e174e4a72 SHA1: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 sha-1: 0e24bc5a548b236e3eb3b22317ef805664a88747c725cd35bfb0db0e4ae5539e3ed5cd5ba8c0ac018deb6518059788c8fffbe624f614fbbe62ba6a6e174e4a72 sha-1: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 blake2b512: d3d661100c5ffb79bdf3b5c77d1698e621414cba40e2348bd3f1b10fbd2fe97bff4dc7d76474955bfefa61179f2a37e9dddedced0e7e79ef9d8c678080d45926 blake2b512: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 RMD160: ec65dbad1485616cf0426725d64e009ad3e1633543746ccb56b7f06eb7ce51d0249aaef27c879f32911a7c0accdc83389c2948ddec439114f6165366f9b4cca2 RMD160: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 RIPEMD-160: ec65dbad1485616cf0426725d64e009ad3e1633543746ccb56b7f06eb7ce51d0249aaef27c879f32911a7c0accdc83389c2948ddec439114f6165366f9b4cca2 RIPEMD-160: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ripemd-160: ec65dbad1485616cf0426725d64e009ad3e1633543746ccb56b7f06eb7ce51d0249aaef27c879f32911a7c0accdc83389c2948ddec439114f6165366f9b4cca2 ripemd-160: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ``` #### Uninitialized memory ```js const { pbkdf2Sync } = require('pbkdf2/browser') // or just 'pbkdf2' on Bun will do this too let prev for (let i = 0; i < 100000; i++) { const key = pbkdf2Sync('secret', 'salt', 100000, 64, 'sha3-256') const hex = key.toString('hex') if (hex !== prev) console.log(hex); prev = hex } ``` ### Affected versions Seems to be since https://github.com/browserify/pbkdf2/commit/9699045c37a07f8319cfb8d44e2ff4252d7a7078 ### Impact This is critical, browserifying code might silently generate zero-filled keys instead of proper ones, for code that was working on Node.js or in test environment Just updating to a fixed version is not enough: if anyone was using `pbkdf2` lib (e.g. via `crypto-browserify` or directly) on algos not from the literal string list (see "were you affected"), recheck where those keys went / how they were used, and take action accordingly ### Note Most likely, you receive this either through a subdep using `pbkdf2` module directly (and then it is used), or through `crypto-browserify` (and the usage depends on whether you or any of your subdeps were calling `pbkdf2/pbkdf2Sync` methods from Node.js crypto inside your bundle) When targeting non-Node.js, prever avoiding Node.js crypto polyfill at all, and use `crypto.subtle` and/or modern/audited cryptography primitives instead
- Source published
- 23 Jun 2025 22:41:50 UTC
- Source modified
- 10 Sep 2026 03:50:25 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H
Publisher rating · CRITICAL