CVE-2026-14570
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCrypt::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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCrypt::DSA versions before 1.22 use a biased random number generator where Crypt::DSA::Util::makerandom forces the high bit of every value, making the top bit fixed and non-uniform. This affects both the DSA signing nonce and private key, allowing an attacker with a modest number of signatures plus the public key to recover the private key via lattice attack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Crypt::DSA is installedRun `perl -MCrypt::DSA -e 'print $Crypt::DSA::VERSION'` or check your Perl library path for the Crypt/DSA.pm moduleAffected if Crypt::DSA is not installed means this CVE does not apply
-
Verify the installed versionCompare the version number from step 1 against the affected range (versions before 1.22)Affected if The version is lower than 1.22 - the library is vulnerable to the biased random number generator
-
Identify if DSA signing operations were performedReview application logs, scripts, or code that use Crypt::DSA for DSA signature generation (the makerandom function is called during signing)Affected if The library was used to generate DSA signatures - the biased nonce could expose private keys
-
Check for existing DSA keysLocate any DSA private or public key files created by or used with Crypt::DSA versions before 1.22Affected if DSA keys exist and were used with the affected library version, they should be considered potentially compromised
You are affected if Crypt::DSA version is installed and is lower than 1.22, and you have used it to perform DSA signing operations or have DSA keys created by this library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Crypt::DSA to version 1.22 or later, and regenerate all DSA keys that were used with affected versions as they should be considered compromised.
Crypt::DSA version 1.22 or later
- Check current Crypt::DSA version: perl -MCrypt::DSA -e 'print $Crypt::DSA::VERSION'
- Upgrade Crypt::DSA to version 1.22 or later using cpan or cpanm: cpan -T Crypt::DSA or cpanm Crypt::DSA
- Verify the new version is installed: perl -MCrypt::DSA -e 'print $Crypt::DSA::VERSION'
- Generate new DSA keys using the updated library - existing keys are compromised
- Re-sign any documents or data that were signed with the affected key version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data