Skip to main content
CVE-2025-6545VulnerabilityPublished

CVE-2025-6545: pbkdf2 · Improper Input Validation

Affects pbkdf2Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
npmpbkdf2pkg:npm/pbkdf2Other threatsAffected
  • =3.0.10
  • <=3.1.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade: Organizations should promptly upgrade pbkdf2 to a patched version beyond 3.1.2 once available. 2. Dependency audit: Conduct a thorough audit of all software dependencies and applications to identify usage of the affected pbkdf2 versions. This includes direct and transitive dependencies in software supply chains. 3. Temporary mitigations: If immediate upgrade is not feasible, consider implementing compensating controls such as additional input validation layers, restricting network access to vulnerable services, and enhanced monitoring for anomalous authentication attempts. 4. Cryptographic verification: Validate the integrity of cryptographic operations by implementing additional signature verification mechanisms or using alternative, trusted cryptographic libraries where possible. 5. Incident response readiness: Prepare for potential exploitation by updating incident response plans to detect and respond to signature spoofing or unauthorized access attempts. 6. Vendor engagement: Engage with software vendors and maintainers to prioritize patch development and deployment. 7. Security testing: Perform penetration testing and code reviews focusing on cryptographic modules to identify similar input validation issues. 8. Awareness and training: Educate development and security teams about the risks of improper input validation in cryptographic functions and best practices for secure coding.

Description

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.

References

Community reviews

Loading reviews…