CVE-2026-9638 | Crypt::PBKDF2 versions before 0.261630 for Perl generate insecure random values for salts

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.

Published: 2026-06-12 Last update: 2026-06-12 Assigner: 9b29abf9-4ab0-4765-b253-1875cd9b441e Source: 9b29abf9-4ab0-4765-b253-1875cd9b441e
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-9638 is rated Low Risk (38.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.32%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-9638

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.32% +0.29%
2 2026-06-13 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-9638

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-9638

GitHub Security Advisory for CVE-2026-9638

GHSA-3rw7-pf56-37cv · Severity: high — Crypt::PBKDF2 versions before 0.261630 for Perl generate insecure random values for salts. These...

OS Trackers for CVE-2026-9638

vendor priority summary link
debian not yet assigned CVE-2026-9638 not yet assigned priority: Debian including 1 source packages (libcrypt-pbkdf2-perl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-9638
suse high CVE-2026-9638 severity important: SUSE including 1 source package names (perl-Crypt-PBKDF2-0.261630-1.1), 1 product×package rows across 1 product lines (openSUSE Tumbleweed): Fixed 1. https://www.suse.com/security/cve/CVE-2026-9638/

Affected software / configurations for CVE-2026-9638

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-9638

cvelogic Threat Intelligence