CVE-2026-4601: jsrsasign · Missing Cryptographic Step
Affects jsrsasignSource CVE Database V5
Public exploit available · CVSS 9.4 Critical : upgrade to 11.1.1 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.1.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:H/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade jsrsasign to 11.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jsrsasign | Affected
| Fixed in
|
| org.webjars.npm:jsrsasign | Affected
| Fixed in– |
npmjsrsasignpkg:npm/jsrsasignOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Currently, Red Hat states that no mitigation is available or that existing options do not meet their criteria for ease of use, deployment, applicability, or stability. If you cannot patch yet, consider avoiding use of the vulnerable jsrsasign versions in security-sensitive contexts or replacing the library with a secure alternative if feasible.
Description
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.
References
- security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370941 (opens in a new tab)
- security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812269 (opens in a new tab)
- gist.github.com/Kr0emer/93789fe6efe5519db9692d4ad1dad586 (opens in a new tab)
- github.com/kjur/jsrsasign/pull/645 (opens in a new tab)
- github.com/kjur/jsrsasign/commit/0710e392ec35de697ce11e4219c988ba2b5fe0eb (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-4601 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2450209 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4601.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19409 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19410 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:6720 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:6568 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19375 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:6912 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:6926 (opens in a new tab)