Skip to content
Fencer Intel
high 7.5

CVE-2026-9638 json

Crypt::PBKDF2 versions before 0.261630 for Perl generate insecure random values for salts

published 4mo ago modified 16d ago also EUVD-2026-36456

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

Summary

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.

Patch / fix

  • ARODLAND Crypt::PBKDF2 0.261630
  • libcrypt-pbkdf2-perl Debian 12 0.261630-1~deb13u1~deb12u1
  • libcrypt-pbkdf2-perl Debian 13 0.261630-1~deb13u1
  • libcrypt-pbkdf2-perl Debian 14 0.261630-1

debian advisories DEBIAN-CVE-2026-9638

  • perl-Crypt-PBKDF2 openSUSE Tumbleweed 0.261630-1.1

opensuse advisories openSUSE-SU-2026:11034-1

Is CVE-2026-9638 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-9638 updated cvss 7.5

perl-Crypt-PBKDF2: generation of insecure random values for salts

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% 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

  • ARODLAND Crypt::PBKDF2

Classification

Weakness
  • CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

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.