CVE-2026-44497

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% 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.4.0 and prior to zebra-script version 6.0.0, the fix for CVE-2026-41583 introduced a separate issue due to insufficient error handling of the case where the sighash type is invalid, during sighash computation. Instead of returning an error, the normal flow would resume, and the input sighash buffer would be left untouched. In scenarios where a previous signature validation could leave a valid sighash in the buffer, an invalid hash-type could be incorrectly accepted, which would create a consensus split between Zebra and zcashd nodes. This issue has been patched in zebrad version 4.4.0 and zebra-script version 6.0.0.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
8.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 due to Stale Buffer · Advisory · ZcashFoundation/zebra · GitHub

Affected: 4.4.0.

https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-gq4h-3grw-2rhv

Affected Packages

(2 across 1 ecosystem)
crates.io(2)
PackageVulnerable rangeFixed inDependents
zebrad4.4.0
zebra-script6.0.0

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-44497?
CVE-2026-44497 is a critical vulnerability published on May 8, 2026. ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.4.0 and prior to zebra-script version 6.0.0, the fix for CVE-2026-41583 introduced a separate issue due to insufficient error handling of the case where the sighash type is invalid, during sighash computation. Instead of…
When was CVE-2026-44497 disclosed?
CVE-2026-44497 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-44497 actively exploited?
CVE-2026-44497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44497?
CVE-2026-44497 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44497?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44497, 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-44497

Explore →

Is Your Infrastructure Affected by CVE-2026-44497?

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