How severe is CVE-2026-47373?

CVE-2026-47373 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-47373 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-47373?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-47373 have an EU (EUVD) identifier?

Yes. CVE-2026-47373 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-31196.

When was CVE-2026-47373 published?

CVE-2026-47373 was published on 2026-05-20 and last updated on 2026-06-17.

CVE-2026-47373

CVE-2026-47373 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-31196
Weakness: CWE-208
Published: 2026-05-20
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-47373?: 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.
How severe is CVE-2026-47373?: CVE-2026-47373 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-47373 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-47373?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-47373 have an EU (EUVD) identifier?: Yes. CVE-2026-47373 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-31196.
When was CVE-2026-47373 published?: CVE-2026-47373 was published on 2026-05-20 and last updated on 2026-06-17.

References

Other CWE-208 vulnerabilities

CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2025-53940 — High (CVSS 8.5): Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central…
CVE-2026-47784 — High (CVSS 8.1): In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because…
CVE-2026-47783 — High (CVSS 8.1): In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a…
CVE-2026-42602 — High (CVSS 8.1): azureauthextension is the Azure Authenticator Extension. From 0.124.0 to 0.150.0, a server-side authentication bypass…

Browse all CWE-208 vulnerabilities →