Crypt::DSA: Reusing a Nonce, Key Pair in Encryption
CVE-2026-12205 is a critical-severity reusing a nonce, key pair in encryption vulnerability in Crypt::DSA from Timlegge, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.21 as the first without the flaw, so updating Crypt::DSA to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.29% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Crypt::DSA to 1.21 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TIMLEGGE | Crypt::DSA | before 1.21 | 1.21 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reusing a Nonce, Key Pair in Encryption
Nonces should be used for the present occasion and only once.
How developers prevent this class of flaw
- Use techniques such as requiring incrementing, time based and/or challenge response to assure uniqueness of nonces.
More Reusing a Nonce, Key Pair in Encryption vulnerabilities (CWE-323)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Crypt::DSA
- 7.5 High severity
- 7.3 High severity
Recent Reusing a Nonce, Key Pair in Encryption vulnerabilities
- 9.1 Critical severity
- 7.1 High severity
- 8.1 High severity
- 7.3 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.