# CVE-2026-14570: Weak cryptography in Crypt::DSA

> Attackers can recover private keys from biased random generation in Crypt::DSA, compromising signed data and requiring key rotation.

- **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:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-14570, GHSA-v6rc-95xw-8xp5, UBUNTU-CVE-2026-14570

## What is CVE-2026-14570?

CVE-2026-14570 is a high-severity vulnerability in TIMLEGGE Crypt::DSA, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crypt::DSA versions before 1.22 for Perl draw the DSA signing nonce and private key from a biased random generator, leading to private-key recovery.

"Crypt::DSA::Util::makerandom forces the high bit of every value it returns to obtain an exactly N-bit integer for prime search. The signing nonce and the private key are drawn from makerandom. Because the high bit is always set, the result is not uniform: its top bit is fixed, producing insecure values."

An attacker who collects a modest number of signatures under an affected key, together with the public key, can recover the private key with a lattice attack.

Keys used to sign with an affected version should be considered compromised and new keys should be generated.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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


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

No fix has been published for CVE-2026-14570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14570 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14570 is a high-severity vulnerability in TIMLEGGE Crypt::DSA, published on 5 Jul 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-14570 in the wild and no public exploit code.

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

## Sources

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

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