CVE-2026-47372VulnerabilityPublished 15 Jun 2026Updated 17 Sep 2026

SUSE · Security update for perl-Crypt-SaltedHash

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-47373

Authoritative record:CVE-2026-47372· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
RRWOCrypt::SaltedHash	Affected <=0.09	Fixed in–
GitHubCrypt-SaltedHash`pkg:github/Crypt-SaltedHash`Other threats	Affected <=0.09	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vulnerabilities are addressed in perl-Crypt-SaltedHash version 0.110.0. Users should update to this version or later to apply the official fixes. Since the module is deprecated, consider migrating to alternative maintained solutions for password hashing.

Description

The perl-Crypt-SaltedHash module was updated to version 0.110.0 to address security issues including the use of a system randomness source for salt generation (CVE-2026-47372) and implementation of constant-time hash comparisons (CVE-2026-47373). These changes improve the security of password hashing by mitigating risks related to predictable salts and timing attacks. The module is now deprecated and maintenance has been taken over by a new maintainer.

Impact

Without these fixes, the perl-Crypt-SaltedHash module could generate salts with insufficient randomness, potentially weakening password hash security. Additionally, lack of constant-time comparison could allow timing attacks to reveal hash information. These vulnerabilities could compromise password confidentiality and authentication integrity.

Summary

This update for perl-Crypt-SaltedHash fixes two security vulnerabilities: CVE-2026-47372, which addresses the use of a system randomness source to generate the salt, enhancing randomness and reducing predictability; and CVE-2026-47373, which implements constant-time comparison of hashes to prevent timing attacks. The update also includes maintenance changes and metadata fixes. No CVSS score is provided, but the issues fixed are critical for cryptographic security.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:20 UTC

Technical details

References

Community reviews

Related threats