[From nobody Tue Jun 16 21:49:06 2026
Received: (at submit) by bugs.debian.org; 12 Jun 2026 19:19:55 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00, FOURLA,
 FROMDEVELOPER, 
 NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 22; hammy, 134; neutral, 31; spammy,
 3. spammytokens:0.993-1--220000, 0.993-1--220,000,
 0.941-+--H*r:bugs.debian.org hammytokens:0.000-+--H*F:U*carnil,
 0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--HTo:N*Debian,
 0.000-+--H*Ad:N*Bug
Return-path: &lt;carnil@debian.org&gt;
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1wY7Q1-004F1E-1d
 for submit@bugs.debian.org; Fri, 12 Jun 2026 19:19:55 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: libcrypt-pbkdf2-perl: CVE-2026-9638 CVE-2026-9641
Message-ID: &lt;178129198820.3931917.14758735107188195622.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0
Date: Fri, 12 Jun 2026 21:19:48 +0200
Delivered-To: submit@bugs.debian.org

Source: libcrypt-pbkdf2-perl
Version: 0.161520-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerabilities were published for libcrypt-pbkdf2-perl.

CVE-2026-9638[0]:
| Crypt::PBKDF2 versions before 0.261630 for Perl generate insecure
| random values for salts.  These versions use the built-in rand
| function, which is predictable and unsuitable for cryptography.


CVE-2026-9641[1]:
| Crypt::PBKDF2 versions before 0.261630 for Perl have a weak default
| algorithm and number of iterations.  The default algorithm is HMAC-
| SHA1, which should only be used for legacy systems.  These versions
| default to using 1000 iterations.  Depending on the chosen
| algorithm, 220,000 to 1,400,000 iterations should be used.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-9638
    https://www.cve.org/CVERecord?id=CVE-2026-9638
[1] https://security-tracker.debian.org/tracker/CVE-2026-9641
    https://www.cve.org/CVERecord?id=CVE-2026-9641

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]