ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a malicious block producer can terminate zebrad by placing the same shielded transaction in a non-finalized parent block and its child. In zebra-state/src/service/non_finalized_state/chain.rs, Chain::push originally inserted the transaction hash into tx_loc_by_hash and asserted uniqueness before updating shielded data and running the duplicate Sprout, Sapling, or Orchard nullifier checks. The repeated transaction therefore reached the transactions must be unique within a single chain assertion before contextual validation could reject it cleanly. Zebra release builds use panic equals abort, so the reachable assertion terminates the entire process; exploitation requires either two consecutive attacker-mined blocks or an attacker-mined child immediately after an honest block includes the attacker's shielded transaction. This issue is fixed in version 4.5.0.
CVE-2026-52739
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 19, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026Repeated Non-Finalized Shielded Transaction Aborts Zebra Before Duplicate-Nullifier Rejection · Advisory · ZcashFoundation/zebra · GitHub
https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-hhm7-qrv5-h4r6Zebra 4.5.0
Patch available: ZcashFoundation/zebra v4.5.0
https://github.com/ZcashFoundation/zebra/releases/tag/v4.5.0commit 1440b43ca7df (ZcashFoundation/zebra)
Patch available: ZcashFoundation/zebra v4.5.0 (contains commit 1440b43ca7df)
https://github.com/ZcashFoundation/zebra/commit/1440b43ca7df59aca948090d45117557b217a6cdVendor Advisories for CVE-2026-52739(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| zebrad | — | 4.5.0 | — |
| zebra-state | — | 7.0.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 13× 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.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:44 UTCEG score recompute
- 2026-08-23 21:02 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:36 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 20:11 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 19:21 UTCEG score recompute
- 2026-08-19 18:23 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:25 UTCEG score recompute
- 2026-07-30 19:13 UTCEG score recompute
- 2026-07-26 13:03 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-02 20:07 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-52739?
When was CVE-2026-52739 disclosed?
Is CVE-2026-52739 actively exploited?
What is the CVSS score of CVE-2026-52739?
How do I remediate CVE-2026-52739?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52739
Is Your Infrastructure Affected by CVE-2026-52739?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.