CVE-2026-4601

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-23) is not newer than that change (2026-09-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-14377 (ENISA EUVD) · GHSA-w8q8-93cx-6h7r (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 23, 2026

Last Modified

September 10, 2026

Advisory Details (10)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat, github_commit, github_pr.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6720
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6568
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19410
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19409
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19375
Web page

Missing Cryptographic Step in jsrsasign | CVE-2026-4601 | Snyk

https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370941
Web page

Missing Cryptographic Step in org.webjars.npm:jsrsasign | CVE-2026-4601 | Snyk

https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812269
GitHub pull request Patch Available

fix(dsa): retry signing when r or s is zero

Patch available: kjur/jsrsasign 11.1.2 (PR #645 merged 2026-02-20)

https://github.com/kjur/jsrsasign/pull/645
GitHub commit Patch Available

commit 0710e392ec35 (kjur/jsrsasign)

Patch available: kjur/jsrsasign 11.1.2 (contains commit 0710e392ec35)

https://github.com/kjur/jsrsasign/commit/0710e392ec35de697ce11e4219c988ba2b5fe0eb

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmigration-toolkit-virtualization/mtv-console-plugin-rhel9:17791398722026-05-19redhat
redhatmigration-toolkit-virtualization/mtv-console-plugin-rhel9:17789274622026-05-19redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatquay/quay-rhel8:17751692182026-04-07redhat
redhatquay/quay-rhel8:17751691552026-04-07redhat
redhatquay/quay-rhel8:17752530922026-04-06redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat
npmjsrsasign @ 11.1.1 (fixes < 11.1.1)—ghsa

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)
PackageVulnerable rangeFix by version rangeDependents
jsrsasign—
  • every version up to 11.1.1: fixed in 11.1.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 81× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 312 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 212 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:12 UTCEG score recompute
  2. 2026-11-02 11:12 UTCVendor advisory
  3. 2026-11-02 11:12 UTCGHSA enrichmentGHSA-w8q8-93cx-6h7r · GitHub severity HIGH · GitHub CVSS 8.7
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-11-01 11:16 UTCVendor advisory
  6. 2026-11-01 11:15 UTCGHSA enrichmentGHSA-w8q8-93cx-6h7r · GitHub severity HIGH · GitHub CVSS 8.7
  7. 2026-11-01 07:48 UTCGHSA enrichmentGHSA-w8q8-93cx-6h7r · GitHub severity HIGH · GitHub CVSS 8.7
  8. 2026-11-01 07:48 UTCEG score recompute
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-31 11:19 UTCEG score recompute
  11. 2026-10-31 11:19 UTCVendor advisory
  12. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-30 11:23 UTCEG score recompute
  14. 2026-10-30 11:23 UTCVendor advisory
  15. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-10-29 11:27 UTCEG score recompute
  17. 2026-10-29 11:27 UTCVendor advisory
  18. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-28 11:31 UTCEG score recompute
  20. 2026-10-28 11:31 UTCVendor advisory
  21. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-10-27 11:09 UTCEG score recompute
  23. 2026-10-27 11:09 UTCVendor advisory
  24. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-10-26 11:13 UTCEG score recompute
Show 75 more
  1. 2026-10-26 11:13 UTCVendor advisory
  2. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-25 14:25 UTCEG score recompute
  4. 2026-10-25 11:18 UTCEG score recompute
  5. 2026-10-25 11:18 UTCVendor advisory
  6. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-24 11:22 UTCEG score recompute
  8. 2026-10-24 11:22 UTCVendor advisory
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-23 11:24 UTCEG score recompute
  11. 2026-10-23 11:24 UTCVendor advisory
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-22 11:24 UTCEG score recompute
  14. 2026-10-22 11:24 UTCVendor advisory
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-21 11:27 UTCEG score recompute
  17. 2026-10-21 11:27 UTCVendor advisory
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-20 11:31 UTCEG score recompute
  20. 2026-10-20 11:31 UTCVendor advisory
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-19 11:33 UTCEG score recompute
  23. 2026-10-19 11:33 UTCVendor advisory
  24. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-18 09:16 UTCVendor advisory
  26. 2026-10-18 03:37 UTCEG score recompute
  27. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-10-17 07:33 UTCEG score recompute
  29. 2026-10-17 07:33 UTCVendor advisory
  30. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-10-16 07:34 UTCEG score recompute
  32. 2026-10-16 07:34 UTCVendor advisory
  33. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  34. 2026-10-15 06:28 UTCEG score recompute
  35. 2026-10-15 06:28 UTCVendor advisory
  36. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  37. 2026-10-14 02:07 UTCEG score recompute
  38. 2026-10-14 02:07 UTCVendor advisory
  39. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  40. 2026-10-12 22:29 UTCEG score recompute
  41. 2026-10-12 22:29 UTCVendor advisory
  42. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  43. 2026-10-12 16:03 UTCEG score recompute
  44. 2026-10-12 07:42 UTCVendor advisory
  45. 2026-10-11 19:46 UTCEG score recompute
  46. 2026-10-11 17:00 UTCEG score recompute
  47. 2026-10-11 14:25 UTCEG score recompute
  48. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  49. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  50. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  52. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  53. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  55. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  56. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  57. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  58. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  59. 2026-09-29 20:02 UTCOSV refresh
  60. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  61. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  62. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  63. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  64. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  65. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  67. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  68. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  69. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  70. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  71. 2026-09-10 13:41 UTCVendor advisory
  72. 2026-09-10 13:36 UTCNVD updateCVSS v4 → 8.8
  73. 2026-09-10 12:28 UTCEG score recompute
  74. 2026-09-10 12:28 UTCVendor advisory
  75. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Frequently asked(5)

What is CVE-2026-4601?
CVE-2026-4601 is a critical-severity vulnerability; its CVE record was published on March 23, 2026. 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…
When was the CVE record for CVE-2026-4601 published?
The CVE record for CVE-2026-4601 was published on March 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-4601 actively exploited?
CVE-2026-4601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4601?
CVE-2026-4601 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-4601?
A fix for CVE-2026-4601 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4601 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4601

Explore →

Is Your Infrastructure Affected by CVE-2026-4601?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.