HighGHSA-w8q8-93cx-6h7rCVE-2026-4601
jsrsasign: Missing cryptographic validation during DSA signing enables private key extraction
Published 23 Mar 2026 · Updated 29 Mar 2026
Affected package
jsrsasignnpm
- Affected
- <11.1.1
- Fixed in
- 11.1.1
Update to the fixed version for your release line, for example:
npm install jsrsasign@11.1.1Details
Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the KJUR.crypto.DSA.signWithMessageHash process in the DSA signing implementation. An attacker can recover the private key by forcing r or s to be zero, so the library emits an invalid signature without retrying, and then solves for x from the resulting signature.
Is GHSA-w8q8-93cx-6h7r in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected jsrsasign, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-4601
- Linkgithub.com/kjur/jsrsasign/pull/645
- Linkgithub.com/kjur/jsrsasign/commit/0710e392ec35de697ce11e4219c988ba2b5fe0eb
- Linkgist.github.com/Kr0emer/93789fe6efe5519db9692d4ad1dad586
- Packagegithub.com/kjur/jsrsasign
- Linksecurity.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370941
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.