CVE-2026-41584

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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-chain version 6.0.2, Orchard transactions contain a rk field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a "zero" value), however, the orchard crate which is used to verify Orchard proofs would panic when fed a rk with the identity value. Thus an attacker could send a crafted transaction that would make a Zebra node crash. This issue has been patched in zebrad version 4.3.1 and zebra-chain version 6.0.2.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
18.5%
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

rk Identity Point Panic in Transaction Verification · Advisory · ZcashFoundation/zebra · GitHub

https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-452v-w3gx-72wg

Affected Packages

(2 across 1 ecosystem)
crates.io(2)
PackageVulnerable rangeFixed inDependents
zebra-chain—6.0.2—
zebrad—4.3.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.

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

Frequently asked(5)

What is CVE-2026-41584?
CVE-2026-41584 is a high 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-chain version 6.0.2, Orchard transactions contain a rk field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a "zero"…
When was CVE-2026-41584 disclosed?
CVE-2026-41584 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-41584 actively exploited?
CVE-2026-41584 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41584?
CVE-2026-41584 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41584?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41584, 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-41584

Explore →

Is Your Infrastructure Affected by CVE-2026-41584?

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

Start Free Scan →Browse All CVEs