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
Elevated
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.3%CVSS: 9.1Exploit: Elevated riskExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
23rd
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: github_commit, github_pr, redhat.
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

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

https://security.snyk.io/vuln/SNYK-JS-JSRSASIGN-15370940
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
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
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
generic

verify forgery.md · GitHub

https://gist.github.com/Kr0emer/bf15ddc097176e951659a24a8e9002a7

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

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: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 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 229 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.1
  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 14:01 UTCEG score recompute
  5. 2026-09-07 14:01 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.1
  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-17 13:47 UTCEPSS rescore
  25. 2026-08-17 12:25 UTCVendor advisory
  26. 2026-08-17 12:25 UTCNVD updateCVSS v4 → 8.1
  27. 2026-08-17 12:13 UTCEG score recompute
  28. 2026-08-17 12:13 UTCVendor advisory
  29. 2026-08-17 12:11 UTCMITRE cvelistV5CVSS v4 → 9.1
  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-14 23:26 UTCVendor advisory
  36. 2026-08-14 19:46 UTCVendor advisory
  37. 2026-08-14 14:19 UTCVendor advisory
  38. 2026-08-14 10:39 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 01:21 UTCVendor advisory
  43. 2026-08-12 21:41 UTCEG score recompute
  44. 2026-08-12 21:41 UTCVendor advisory
  45. 2026-08-12 13:51 UTCEPSS rescore
  46. 2026-08-12 12:39 UTCVendor advisory
  47. 2026-08-12 12:36 UTCNVD updateCVSS v4 → 8.1
  48. 2026-08-12 12:14 UTCVendor advisory
  49. 2026-08-12 00:55 UTCVendor advisory
  50. 2026-08-11 21:15 UTCEG score recompute
  51. 2026-08-11 21:15 UTCVendor advisory
  52. 2026-08-11 07:59 UTCVendor advisory
  53. 2026-08-11 04:18 UTCEG score recompute
  54. 2026-08-11 04:18 UTCVendor advisory
  55. 2026-08-11 00:00 UTCEPSS rescore
  56. 2026-08-10 12:13 UTCVendor advisory
  57. 2026-08-10 07:40 UTCVendor advisory
  58. 2026-08-10 04:00 UTCVendor advisory
  59. 2026-08-10 00:20 UTCVendor advisory
  60. 2026-08-09 20:40 UTCVendor advisory
  61. 2026-08-09 17:00 UTCEG score recompute
  62. 2026-08-09 17:00 UTCVendor advisory
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-09 13:19 UTCVendor advisory
  65. 2026-08-09 06:35 UTCEG score recompute
  66. 2026-08-09 06:35 UTCVendor advisory
  67. 2026-08-08 16:37 UTCEPSS rescore
  68. 2026-08-08 11:25 UTCVendor advisory
  69. 2026-08-08 07:37 UTCVendor advisory
  70. 2026-08-08 03:57 UTCVendor advisory
  71. 2026-08-08 00:17 UTCVendor advisory
  72. 2026-08-07 20:37 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-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 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-4600 actively exploited?
CVE-2026-4600 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-4600?
CVE-2026-4600 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-4600?
A fix for CVE-2026-4600 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4600 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-4600

Explore →

Is Your Infrastructure Affected by CVE-2026-4600?

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

Book a Demo →Browse All CVEs