Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-14570: CWE-330 Use of Insufficiently Random Values in TIMLEGGE Crypt::DSA

0
High
VulnerabilityCVE-2026-14570cvecve-2026-14570cwe-330
Published: 07/05/2026 (07/05/2026, 01:30:12 UTC)
Source: CVE Database V5
Vendor/Project: TIMLEGGE
Product: Crypt::DSA

Description

Crypt::DSA versions before 1.22 for Perl use a biased random number generator for DSA signing nonces and private keys, leading to private key recovery. The high bit of every random value is forced to 1, resulting in non-uniform, insecure values. An attacker with a modest number of signatures and the public key can recover the private key using a lattice attack. Keys generated with affected versions should be considered compromised and replaced.

Affected software

GitHub Actionsmore threats →cve
Crypt-DSA
pkg:github/Crypt-DSA
Affected versions
<1.22

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/05/2026, 02:07:16 UTC

Technical Analysis

Crypt::DSA versions prior to 1.22 use Crypt::DSA::Util::makerandom to generate DSA signing nonces and private keys. This function forces the high bit of every generated value to be set, producing biased, non-uniform random numbers. This bias weakens the cryptographic strength of the keys and nonces, enabling an attacker who collects a modest number of signatures and has access to the public key to recover the private key via a lattice attack. This vulnerability is classified as CWE-330 (Use of Insufficiently Random Values).

Potential Impact

The vulnerability allows an attacker to recover the private key from signatures generated by affected versions of Crypt::DSA. This compromises the confidentiality and integrity of signatures, enabling forgery and impersonation. Keys used with affected versions must be considered compromised.

Mitigation Recommendations

No official patch or remediation level is provided in the advisory. Users should upgrade to Crypt::DSA version 1.22 or later where this issue is fixed. All keys generated with affected versions should be considered compromised and replaced with new keys generated using a fixed version.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
CPANSec
Date Reserved
2026-07-03T10:37:19.787Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a49b8d527e9c79719b72a73

Added to database: 07/05/2026, 01:52:21 UTC

Last enriched: 07/05/2026, 02:07:16 UTC

Last updated: 07/05/2026, 03:53:31 UTC

Views: 28

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses