Skip to content
Fencer Intel
high 7.5

CVE-2026-47373 json

Crypt::SaltedHash versions through 0.09 for Perl is susceptible to timing attacks

published 5mo ago modified 3mo ago also EUVD-2026-31196

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

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.

Patch / fix

  • libcrypt-saltedhash-perl Debian 14 0.11-1

debian advisories DEBIAN-CVE-2026-47373

  • perl-Crypt-SaltedHash openSUSE Leap 16.0 0.110.0-bp160.1.1
  • perl-Crypt-SysRandom openSUSE Leap 16.0 0.7.0-bp160.1.1
  • perl-Crypt-SaltedHash openSUSE Tumbleweed 0.110.0-1.1

opensuse advisories openSUSE-SU-2026:20986-1openSUSE-SU-2026:10836-1

Is CVE-2026-47373 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • RRWO Crypt::SaltedHash

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.