CVE-2026-4601

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%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 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 computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

Published

March 23, 2026

Last Modified

September 10, 2026

Advisory Details (10)

Auto-updated Sep 15, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: redhat, github_commit, github_pr.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6720
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6568
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19410
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19409
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19375
generic🔴 Active Exploitation

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

https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370941
generic🔴 Active Exploitation

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

https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812269
github_pr 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
generic

sign s zero.md · GitHub

https://gist.github.com/Kr0emer/93789fe6efe5519db9692d4ad1dad586

Vendor Advisories for CVE-2026-4601(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

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

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 7× in last 7d / 23× 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 238 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-4601?
CVE-2026-4601 is a critical vulnerability 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 CVE-2026-4601 disclosed?
CVE-2026-4601 was first published on March 23, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4601 actively exploited?
CVE-2026-4601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th 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.

Book a Demo →Browse All CVEs