jsrsasign: DSA signatures or X.509 certificates can be forged via DSA domain-parameter validation in KJUR.crypto.DSA.setPublic
Published 23 Mar 2026 · Updated 21 Jul 2026
Affected package
- Affected
- <11.1.1
- Fixed in
- 11.1.1
npm install jsrsasign@11.1.1Details
Versions of the package jsrsasign before 11.1.1 are vulnerable to Improper Verification of Cryptographic Signature via the DSA domain-parameter validation in KJUR.crypto.DSA.setPublic (and the related DSA/X509 verification flow in src/dsa-2.0.js). An attacker can forge DSA signatures or X.509 certificates that X509.verifySignature() accepts by supplying malicious domain parameters such as g=1, y=1, and a fixed r=1, which make the verification equation true for any hash.
Is GHSA-wvqx-v3f6-w8rh 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-4600
- Linkgithub.com/kjur/jsrsasign/pull/646
- Linkgithub.com/kjur/jsrsasign/commit/37b4c06b145c7bfd6bc2a6df5d0a12c56b15ef60
- Linksecurity.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370940
- Linksecurity.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812268
- Linksecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4600.json
- Packagegithub.com/kjur/jsrsasign
- Linkgist.github.com/Kr0emer/bf15ddc097176e951659a24a8e9002a7
- Linkbugzilla.redhat.com/show_bug.cgi?id=2450208
- Linkaccess.redhat.com/security/cve/CVE-2026-4600
- Linkaccess.redhat.com/errata/RHSA-2026:6926
- Linkaccess.redhat.com/errata/RHSA-2026:6912
- Linkaccess.redhat.com/errata/RHSA-2026:6720
- Linkaccess.redhat.com/errata/RHSA-2026:6568
- Linkaccess.redhat.com/errata/RHSA-2026:19410
- Linkaccess.redhat.com/errata/RHSA-2026:19409
- Linkaccess.redhat.com/errata/RHSA-2026:19375
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.