# CVE-2026-6659: Crypt::PasswdMD5 versions through 1.42 for Perl generates insecure random values for salts

> Attackers can predict password salts due to insecure random generation, potentially facilitating password cracking attacks against systems 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:** 8 May 2026
- **Updated:** 26 May 2026
- **Also known as:** AZL-86411, DEBIAN-CVE-2026-6659, GHSA-j539-xxc6-73wf, UBUNTU-CVE-2026-6659, openSUSE-SU-2026:11000-1, openSUSE-SU-2026:21137-1

## What is CVE-2026-6659?

CVE-2026-6659 is a high-severity vulnerability in RSAVAGE Crypt::PasswdMD5, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crypt::PasswdMD5 versions through 1.42 for Perl generates insecure random values for salts.

The built-in rand function is predictable, and unsuitable for cryptography.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Crypt-PasswdMD5` | openSUSE:Leap 16.0 | All versions | 1.430.0-bp160.1.1 |
| `perl-Crypt-PasswdMD5` | openSUSE:Tumbleweed | All versions | 1.430.0-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-6659 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6659 is a high-severity vulnerability in RSAVAGE Crypt::PasswdMD5, published on 8 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-6659 in the wild and no public exploit code.

Affected product: RSAVAGE Crypt::PasswdMD5. 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-6659/ (Markdown: https://insights.sbomify.com/CVE-2026-6659/index.md)
```

## Sources

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

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