Password cracking via weak PBKDF2 defaults
Published Jun 12, 2026 · Updated Jun 12, 2026
Insufficient password-hash strength in Crypt::PBKDF2 before 0.261630 allows attackers to crack exposed hashes with less effort. The module's hash_class and iterations defaults select HMAC-SHA1 and only 1,000 PBKDF2 rounds when applications omit overrides. Exploitation requires access to hashes produced with those defaults; hashes created with explicitly stronger settings do not share this weakness.
Summary
What happened
Insufficient password-hash strength in Crypt::PBKDF2 before 0.261630 allows attackers to crack exposed hashes with less effort. The module's hash_class and iterations defaults select HMAC-SHA1 and only 1,000 PBKDF2 rounds when applications omit overrides. Exploitation requires access to hashes produced with those defaults; hashes created with explicitly stronger settings do not share this weakness.
The record
- CVE
- CVE-2026-9641
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- Andrew Rodland
- Product
- Crypt::PBKDF2
- Classifications
- CWE-916, T1110.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.261630
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo