CVE-2026-4600

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this weekElevated
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: Elevated riskExposed: 0

A fix is available — apply it.

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.

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 computed
Severity91% × 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, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_pr, github_commit.
github_commit Patch Available

commit 37b4c06b145c (kjur/jsrsasign)

Patch available: kjur/jsrsasign 11.1.2 (contains commit 37b4c06b145c)

https://github.com/kjur/jsrsasign/commit/37b4c06b145c7bfd6bc2a6df5d0a12c56b15ef60
github_pr Patch Available

fix(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/646
generic🔴 Active Exploitation

Improper Verification of Cryptographic Signature in org.webjars.npm:jsrsasign | CVE-2026-4600 | Snyk

https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15812268
generic🔴 Active Exploitation

Improper Verification of Cryptographic Signature in jsrsasign | CVE-2026-4600 | Snyk

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

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:17751691552026-04-07redhat
redhatquay/quay-rhel8:17751692182026-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
jsrsasign11.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.

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

Frequently asked(5)

What is CVE-2026-4600?
CVE-2026-4600 is a critical vulnerability published on March 23, 2026. 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…
When was CVE-2026-4600 disclosed?
CVE-2026-4600 was first published in the National Vulnerability Database on March 23, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4600 actively exploited?
CVE-2026-4600 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 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-4600?
CVE-2026-4600 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-4600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4600, 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-4600

Explore →

Is Your Infrastructure Affected by CVE-2026-4600?

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