# CVE-2026-47373: Crypt::SaltedHash versions through 0.09 for Perl is susceptible to timing attacks

> Attackers can exploit timing discrepancies in hash comparison to guess underlying hashes, compromising data confidentiality in applications using this Perl library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** DEBIAN-CVE-2026-47373, GHSA-mjc4-qqxc-7h36, UBUNTU-CVE-2026-47373

## What is CVE-2026-47373?

CVE-2026-47373 is a high-severity vulnerability in RRWO Crypt::SaltedHash, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2026-47373?


## How do I fix CVE-2026-47373?

Upgrade to a fixed version.

## Is CVE-2026-47373 being exploited?

There is no known exploitation of CVE-2026-47373 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47373 and fix it if it is affected.

What it is: CVE-2026-47373 is a high-severity vulnerability in RRWO Crypt::SaltedHash, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47373 in the wild and no public exploit code.

Affected product: RRWO Crypt::SaltedHash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47373/ (Markdown: https://insights.sbomify.com/CVE-2026-47373/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47373
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47373
- OSV: https://osv.dev/vulnerability/CVE-2026-47373

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47373/
Summaries are generated and may contain mistakes; the official description above is the record.