https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-01T02:45:32.592795+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2025-6545 CVE-2025-6545 — pbkdf2 silently returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos supporte… 2026-10-01T02:45:32.721814+00:00

Affected: pbkdf2

Improper 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.

 https://vulnerability.circl.lu/vuln/ghsa-h7cp-r72f-jxh6 GHSA-h7cp-r72f-jxh6 — pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos 2026-10-01T02:45:32.721940+00:00

Affected: npm: pbkdf2

### 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

T…