CVE-2026-4600

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% 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
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 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
7.4
EG Score
7.4(medium)
EPSS
13.1%
KEV
Not listed

Published

March 23, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jun 22, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_pr, github_commit.
generic

verify forgery.md · GitHub

https://gist.github.com/Kr0emer/bf15ddc097176e951659a24a8e9002a7
generic🔴 Active Exploitation

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

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

Vendor Advisories for CVE-2026-4600(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: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
jsrsasign—11.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 / 42× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-4600?
CVE-2026-4600 is a high 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 July 7, 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 13.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4600?
CVE-2026-4600 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending).
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.

Start Free Scan →Browse All CVEs