DSA private-key recovery via zero-component signatures
Published Mar 23, 2026 · Updated Mar 23, 2026
Missing cryptographic step in jsrsasign before 11.1.1 allows attackers to recover DSA private keys from invalid signatures. KJUR.crypto.DSA.signWithMessageHash returns signatures when r or s equals zero instead of generating a new ephemeral k and retrying. Exposure requires an application to use the affected DSA signing path and an attacker to obtain a zero-component signature; one such signature reveals x.
Summary
What happened
Missing cryptographic step in jsrsasign before 11.1.1 allows attackers to recover DSA private keys from invalid signatures. KJUR.crypto.DSA.signWithMessageHash returns signatures when r or s equals zero instead of generating a new ephemeral k and retrying. Exposure requires an application to use the affected DSA signing path and an attacker to obtain a zero-component signature; one such signature reveals x.
The record
- CVE
- CVE-2026-4601
- Published
- Mar 23, 2026
- Updated
- Mar 23, 2026
- Vendor
- jsrsasign project
- Product
- jsrsasign
- Classifications
- CWE-325
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2026CVE publishedPublication date reported by the CVE source.
- Mar 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <11.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- DSA zero-component signature key-recovery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo