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.
CVE-2026-4600
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 57(Track*)EG Risk 57/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
March 23, 2026
Last Modified
August 24, 2026
Advisory Details (5)
Auto-updated Aug 1, 2026commit 37b4c06b145c (kjur/jsrsasign)
Patch available: kjur/jsrsasign 11.1.2 (contains commit 37b4c06b145c)
https://github.com/kjur/jsrsasign/commit/37b4c06b145c7bfd6bc2a6df5d0a12c56b15ef60fix(dsa): reject invalid domain parameters to prevent universal signature forgery
Patch available: kjur/jsrsasign 11.1.2 (PR #646 merged 2026-02-20)
https://github.com/kjur/jsrsasign/pull/646Improper Verification of Cryptographic Signature in org.webjars.npm:jsrsasign | CVE-2026-4600 | Snyk
https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812268Improper Verification of Cryptographic Signature in jsrsasign | CVE-2026-4600 | Snyk
https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370940Vendor Advisories for CVE-2026-4600(8)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:19410Red Hat Product SecurityHigh
Red Hat Security Advisory: MTV RHEL9 Images
- RHSA-2026:19409Red Hat Product SecurityHigh
Red Hat Security Advisory: MTV RHEL9 Images
- RHSA-2026:19375Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.16.4
- RHSA-2026:6926Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.9.20
- RHSA-2026:6912Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.10.20
- RHSA-2026:6720Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.12.16
- RHSA-2026:6568Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.15.4
- GHSA-wvqx-v3f6-w8rhGitHub Security AdvisoriesHigh
jsrsasign: DSA signatures or X.509 certificates can be forged via DSA domain-parameter validation in KJUR.crypto.DSA.setPublic
Patch Availability(7)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | migration-toolkit-virtualization/mtv-console-plugin-rhel9:1779139872 | 2026-05-19 | redhat |
| redhat | migration-toolkit-virtualization/mtv-console-plugin-rhel9:1778927462 | 2026-05-19 | redhat |
| redhat | quay/quay-rhel9:1779204086 | 2026-05-19 | redhat |
| redhat | quay/quay-rhel8:1775169155 | 2026-04-07 | redhat |
| redhat | quay/quay-rhel8:1775169218 | 2026-04-07 | redhat |
| redhat | quay/quay-rhel8:1775253092 | 2026-04-06 | redhat |
| redhat | quay/quay-rhel8:1775169219 | 2026-04-03 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jsrsasign | — | 11.1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 85× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 189 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 12:27 UTCEG score recompute
- 2026-08-24 12:27 UTCVendor advisory
- 2026-08-24 12:20 UTCMITRE cvelistV5CVSS v4 → 9.1
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:25 UTCVendor advisory
- 2026-08-17 12:25 UTCNVD updateCVSS v4 → 8.1
- 2026-08-17 12:13 UTCEG score recompute
- 2026-08-17 12:13 UTCVendor advisory
- 2026-08-17 12:11 UTCMITRE cvelistV5CVSS v4 → 9.1
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:49 UTCEG score recompute
- 2026-08-16 10:49 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:26 UTCVendor advisory
- 2026-08-14 19:46 UTCVendor advisory
- 2026-08-14 14:19 UTCVendor advisory
- 2026-08-14 10:39 UTCVendor advisory
- 2026-08-14 06:59 UTCEG score recompute
- 2026-08-14 06:59 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:21 UTCVendor advisory
- 2026-08-12 21:41 UTCEG score recompute
- 2026-08-12 21:41 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:39 UTCVendor advisory
- 2026-08-12 12:36 UTCNVD updateCVSS v4 → 8.1
- 2026-08-12 12:14 UTCVendor advisory
- 2026-08-12 00:55 UTCVendor advisory
- 2026-08-11 21:15 UTCEG score recompute
- 2026-08-11 21:15 UTCVendor advisory
- 2026-08-11 07:59 UTCVendor advisory
- 2026-08-11 04:18 UTCEG score recompute
- 2026-08-11 04:18 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:13 UTCVendor advisory
- 2026-08-10 07:40 UTCVendor advisory
- 2026-08-10 04:00 UTCVendor advisory
- 2026-08-10 00:20 UTCVendor advisory
- 2026-08-09 20:40 UTCVendor advisory
- 2026-08-09 17:00 UTCEG score recompute
- 2026-08-09 17:00 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 13:19 UTCVendor advisory
- 2026-08-09 06:35 UTCEG score recompute
- 2026-08-09 06:35 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 11:25 UTCVendor advisory
- 2026-08-08 07:37 UTCVendor advisory
- 2026-08-08 03:57 UTCVendor advisory
- 2026-08-08 00:17 UTCVendor advisory
- 2026-08-07 20:37 UTCVendor advisory
- 2026-08-07 16:57 UTCEG score recompute
- 2026-08-07 16:57 UTCVendor advisory
- 2026-08-06 19:13 UTCEG score recompute
- 2026-08-06 19:13 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 08:39 UTCVendor advisory
- 2026-08-06 04:58 UTCVendor advisory
- 2026-08-06 01:18 UTCEG score recompute
- 2026-08-06 01:18 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 04:11 UTCVendor advisory
- 2026-08-04 00:17 UTCVendor advisory
- 2026-08-03 12:49 UTCEG score recompute
- 2026-08-03 12:49 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 23:18 UTCVendor advisory
- 2026-08-02 19:37 UTCVendor advisory
- 2026-08-02 15:57 UTCEG score recompute
- 2026-08-02 15:57 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 16:38 UTCEG score recompute
- 2026-07-27 16:38 UTCVendor advisory
- 2026-07-27 16:16 UTCMITRE cvelistV5CVSS v4 → 9.1
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:16 UTCEG score recompute▲ 1.70
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 12:36 UTCNVD updateCVSS v3 → 9.1 · CVSS v4 → 8.1 · severity → CRITICAL
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 07:16 UTCOSV refresh
- 2026-07-16 17:03 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-4600?
When was CVE-2026-4600 disclosed?
Is CVE-2026-4600 actively exploited?
What is the CVSS score of CVE-2026-4600?
How do I remediate CVE-2026-4600?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4600
Is Your Infrastructure Affected by CVE-2026-4600?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.