[From nobody Thu May 21 21:53:07 2026
Received: (at submit) by bugs.debian.org; 21 May 2026 19:16:36 +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=-11.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 MD5_SHA1_SUM,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, 30; hammy, 145; neutral, 32; spammy,
 1. spammytokens: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 1wQ8si-00DeY9-2u
 for submit@bugs.debian.org; Thu, 21 May 2026 19:16:36 +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-saltedhash-perl: CVE-2026-47372 CVE-2026-47373
Message-ID: &lt;177939099185.479912.13680075241806429403.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0
Date: Thu, 21 May 2026 21:16:31 +0200
Delivered-To: submit@bugs.debian.org

Source: libcrypt-saltedhash-perl
Version: 0.09-3
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-saltedhash-perl.

CVE-2026-47372[0]:
| Crypt::SaltedHash versions through 0.09 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-47373[1]:
| Crypt::SaltedHash versions through 0.09 for Perl is susceptible to
| timing attacks.  These versions use Perl's built-in eq comparison.
| Discrepencies in timing could be used to guess the underlying hash.


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-47372
    https://www.cve.org/CVERecord?id=CVE-2026-47372
    https://lists.security.metacpan.org/cve-announce/msg/40252126/
    https://github.com/robrwo/perl-Crypt-SaltedHash/commit/9b68437d2cd420b819b3a795474c3870338d38d5
[1] https://security-tracker.debian.org/tracker/CVE-2026-47373
    https://www.cve.org/CVERecord?id=CVE-2026-47373
    https://lists.security.metacpan.org/cve-announce/msg/40249915/
    https://github.com/robrwo/perl-Crypt-SaltedHash/commit/c07bfc5c23185b0667233d0f2e1252d81f1f027a

Regards,
Salvatore
]