CVE-2026-9641: CWE-916 Use of Password Hash With Insufficient Computational Effort in ARODLAND Crypt::PBKDF2
Crypt::PBKDF2 versions prior to 0.261630 for Perl use a weak default password hashing configuration. The default algorithm is HMAC-SHA1, which is intended only for legacy systems, and the default iteration count is 1000. Recommended iteration counts range from 220,000 to 1,400,000 depending on the algorithm chosen. This weak configuration can reduce the computational effort required to crack password hashes.
AI Analysis
Technical Summary
CVE-2026-9641 identifies a weakness in Crypt::PBKDF2 versions before 0.261630 where the default password hashing algorithm is HMAC-SHA1 with only 1000 iterations. This is insufficient computational effort for modern security standards, as recommended iterations are significantly higher (220,000 to 1,400,000). This vulnerability falls under CWE-916, indicating the use of password hashing with insufficient computational effort, which can facilitate faster brute-force attacks against hashed passwords.
Potential Impact
The weak default algorithm and low iteration count reduce the time and resources required for an attacker to perform brute-force or dictionary attacks on password hashes generated by affected versions. This can lead to compromised password confidentiality if hashes are obtained. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation level has been published yet. Users should upgrade to version 0.261630 or later when available. Until then, users should manually configure Crypt::PBKDF2 to use a stronger algorithm than HMAC-SHA1 and increase the iteration count to at least 220,000 or higher depending on the algorithm. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-9641: CWE-916 Use of Password Hash With Insufficient Computational Effort in ARODLAND Crypt::PBKDF2
Description
Crypt::PBKDF2 versions prior to 0.261630 for Perl use a weak default password hashing configuration. The default algorithm is HMAC-SHA1, which is intended only for legacy systems, and the default iteration count is 1000. Recommended iteration counts range from 220,000 to 1,400,000 depending on the algorithm chosen. This weak configuration can reduce the computational effort required to crack password hashes.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9641 identifies a weakness in Crypt::PBKDF2 versions before 0.261630 where the default password hashing algorithm is HMAC-SHA1 with only 1000 iterations. This is insufficient computational effort for modern security standards, as recommended iterations are significantly higher (220,000 to 1,400,000). This vulnerability falls under CWE-916, indicating the use of password hashing with insufficient computational effort, which can facilitate faster brute-force attacks against hashed passwords.
Potential Impact
The weak default algorithm and low iteration count reduce the time and resources required for an attacker to perform brute-force or dictionary attacks on password hashes generated by affected versions. This can lead to compromised password confidentiality if hashes are obtained. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation level has been published yet. Users should upgrade to version 0.261630 or later when available. Until then, users should manually configure Crypt::PBKDF2 to use a stronger algorithm than HMAC-SHA1 and increase the iteration count to at least 220,000 or higher depending on the algorithm. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-05-26T18:44:37.132Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c283de617e2d83487db49
Added to database: 6/12/2026, 3:39:41 PM
Last enriched: 6/12/2026, 3:55:38 PM
Last updated: 6/12/2026, 5:05:30 PM
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.