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
Trending — 5 sources updated this week
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%CVSS: 9.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
41(Track)
EG Risk 41/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 computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

March 23, 2026

Last Modified

July 26, 2026

Advisory Details (4)

Auto-updated May 3, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

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

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

fix(dsa): retry signing when r or s is zero by Kr0emer · Pull Request #645 · kjur/jsrsasign · GitHub

https://github.com/kjur/jsrsasign/pull/645
generic

Merge pull request #645 from Kr0emer/fix/bug-001-sign_s_zero · kjur/jsrsasign@0710e39 · GitHub

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 / EcosystemFixed in / 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 rangeFixed inDependents
jsrsasign—11.1.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 46× 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 111 total refreshes for this CVE.

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

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 in the National Vulnerability Database on March 23, 2026, with the most recent update on July 26, 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% probability of exploitation in the next 30 days, which ranks it in the top 77.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4601, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs