CVE-2026-12205: CWE-323 Reusing a Nonce, Key Pair in Encryption in TIMLEGGE Crypt::DSA
Crypt::DSA versions before 1.21 for Perl reused the nonce across signatures, leading to private-key recovery. Crypt::DSA::sign caches the per-signature nonce material in the Key object without ever clearing it. The first sign() on a Key object picks a nonce, and every later sign() on that same object reuses it, producing an identical "r". Keys used to sign more than once with an affected version should be considered compromised.
AI Analysis
Technical Summary
The Crypt::DSA Perl module prior to version 1.21 improperly manages the nonce used in DSA signatures by caching it in the Key object without clearing it. The first signature generates a nonce, but subsequent signatures reuse the same nonce, producing identical 'r' values in signatures. This nonce reuse violates cryptographic best practices and enables attackers to recover the private key from multiple signatures made with the same nonce. Keys used multiple times with affected versions are therefore compromised.
Potential Impact
Private keys used with Crypt::DSA versions before 1.21 can be recovered if the same key object signs more than one message, due to nonce reuse. This compromises the confidentiality and integrity guarantees of the digital signature scheme, potentially allowing attackers to forge signatures or impersonate the key owner.
Mitigation Recommendations
No official patch or remediation level is provided in the available data. Users should upgrade to Crypt::DSA version 1.21 or later where this issue is fixed. Until then, keys should not be reused for signing multiple messages with affected versions. Check the vendor advisory for any updates on patches or fixes.
CVE-2026-12205: CWE-323 Reusing a Nonce, Key Pair in Encryption in TIMLEGGE Crypt::DSA
Description
Crypt::DSA versions before 1.21 for Perl reused the nonce across signatures, leading to private-key recovery. Crypt::DSA::sign caches the per-signature nonce material in the Key object without ever clearing it. The first sign() on a Key object picks a nonce, and every later sign() on that same object reuses it, producing an identical "r". Keys used to sign more than once with an affected version should be considered compromised.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Crypt::DSA Perl module prior to version 1.21 improperly manages the nonce used in DSA signatures by caching it in the Key object without clearing it. The first signature generates a nonce, but subsequent signatures reuse the same nonce, producing identical 'r' values in signatures. This nonce reuse violates cryptographic best practices and enables attackers to recover the private key from multiple signatures made with the same nonce. Keys used multiple times with affected versions are therefore compromised.
Potential Impact
Private keys used with Crypt::DSA versions before 1.21 can be recovered if the same key object signs more than one message, due to nonce reuse. This compromises the confidentiality and integrity guarantees of the digital signature scheme, potentially allowing attackers to forge signatures or impersonate the key owner.
Mitigation Recommendations
No official patch or remediation level is provided in the available data. Users should upgrade to Crypt::DSA version 1.21 or later where this issue is fixed. Until then, keys should not be reused for signing multiple messages with affected versions. Check the vendor advisory for any updates on patches or fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-06-14T12:07:30.610Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a307d3d0b89be6888adcd1b
Added to database: 6/15/2026, 10:31:25 PM
Last enriched: 6/15/2026, 10:45:36 PM
Last updated: 6/15/2026, 11:50:21 PM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.