CVE-2026-41583

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade. Zebra nodes could thus accept and eventually mine a block that would be considered invalid by zcashd nodes, creating a consensus split between Zebra and zcashd nodes. In a similar vein, for V4 transactions, Zebra mistakenly used the "canonical" hash type when computing the sighash while zcashd (correctly per the spec) uses the raw value, which could also crate a consensus split. This issue has been patched in zebrad version 4.3.1 and zebra-script version 5.0.2.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
19.6%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 8, 2026

Advisory Details (1)

Auto-updated May 8, 2026
Patch available. Sources: github.
github Patch Available

Consensus Divergence in Transparent Sighash Hash-Type Handling · Advisory · ZcashFoundation/zebra · GitHub

https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-8m29-fpq5-89jj

Affected Packages

(2 across 1 ecosystem)
crates.io(2)
PackageVulnerable rangeFixed inDependents
zebrad—4.3.1—
zebra-script—5.0.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 52× 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 153 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41583?
CVE-2026-41583 is a critical vulnerability published on May 8, 2026. ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network…
When was CVE-2026-41583 disclosed?
CVE-2026-41583 was first published in the National Vulnerability Database on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41583 actively exploited?
CVE-2026-41583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41583?
CVE-2026-41583 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-41583?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41583, 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-41583

Explore →

Is Your Infrastructure Affected by CVE-2026-41583?

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

Start Free Scan →Browse All CVEs