Microsoft · Crypt::PBKDF2 versions before 0.261630 for Perl have a weak default algorithm and number of iterations
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.261630 when convenient.
Data as of 17 Nov 2026, 11:48 UTC
- Patch
- Available – fixed in 0.261630
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade Crypt::PBKDF2 and Crypt-PBKDF2 to 0.261630.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ARODLANDCrypt::PBKDF2 | Affected
| Fixed in
|
GitHubCrypt-PBKDF2pkg:github/Crypt-PBKDF2Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Avoid relying on default settings for cryptographic parameters and consider configuring stronger algorithms and higher iteration counts if possible.
Description
Crypt::PBKDF2 versions before 0.261630 for Perl use a weak default algorithm and insufficient number of iterations, potentially reducing the effectiveness of password-based key derivation.