CVE-2026-4600: jsrsasign · Improper Verification of Cryptographic Signature
Affects jsrsasignSource CVE Database V5
Public exploit available · CVSS 9.1 Critical : upgrade to 11.1.1 as a priority.
Data as of 30 Oct 2026, 06:59 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% 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:N/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 29 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
According to the Red Hat advisory, no effective mitigation or patch currently meets their criteria for ease of use, applicability, or stability. Upgrading to jsrsasign version 11.1.1 or later, where this vulnerability is fixed, is recommended when feasible. For affected Red Hat products, consult Red Hat support or your Technical Account Manager for guidance. No temporary workaround is provided.
Description
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.
References
- security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370940 (opens in a new tab)
- security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812268 (opens in a new tab)
- gist.github.com/Kr0emer/bf15ddc097176e951659a24a8e9002a7 (opens in a new tab)
- github.com/kjur/jsrsasign/pull/646 (opens in a new tab)
- github.com/kjur/jsrsasign/commit/37b4c06b145c7bfd6bc2a6df5d0a12c56b15ef60 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-4600 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2450208 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4600.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)