CVE-2026-47373: Crypt::SaltedHash versions through 0.09 for Perl is susceptible to timing attacks
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: libcrypt-saltedhash-perl (Debian:14) 0.11-1; 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.
Low priority for now. Upgrade to libcrypt-saltedhash-perl (Debian:14) 0.11-1; 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 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 20, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-208
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CPANSec). Independent of NVD's CPE analysis and usually ahead of it.
RRWO Crypt::SaltedHash
- up to and including 0.09affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libcrypt-saltedhash-perl | from 0 | — |
| Debian:14 | libcrypt-saltedhash-perl | before 0.11-1 | 0.11-1 |
| openSUSE:Leap 16.0 | perl-Crypt-SaltedHash | before 0.110.0-bp160.1.1 | 0.110.0-bp160.1.1 |
| openSUSE:Leap 16.0 | perl-Crypt-SysRandom | before 0.7.0-bp160.1.1 | 0.7.0-bp160.1.1 |
| openSUSE:Tumbleweed | perl-Crypt-SaltedHash | before 0.110.0-1.1 | 0.110.0-1.1 |
Same product
rrwo: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-47372Crypt::SaltedHash versions through 0.09 for Perl generate insecure random values for salts36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libcrypt-saltedhash-perl | 0.11-1 · Debian:14 | Package registry (OSV) |
| opensuse:perl-Crypt-SaltedHash | 0.110.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:perl-Crypt-SysRandom | 0.7.0-bp160.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-208 · Observable Timing DiscrepancyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.