ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a remote unauthenticated P2P peer can stall a Zebra node by racing an invalid block body against the valid canonical body for the same block header hash. ZIP-244 permits the attacker to mutate coinbase scriptSig authentication data while retaining the transaction identifiers, merkle root, and block header hash, so the poisoned body fails later commitment validation but shares the canonical hash. In zebra-state/src/service.rs, queue_and_commit_to_non_finalized_state recorded the hash in non_finalized_block_write_sent_hashes before contextual validation completed and did not remove it when the write task rejected the body. When the honest body later arrived, the cached hash caused KnownBlock::WriteChannel duplicate handling to suppress it, leaving the node stuck one height behind until restart or reorganization. This issue is fixed in version 4.5.0.
CVE-2026-52736
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity87% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 18, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026Zebra 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/1440b43ca7df59aca948090d45117557b217a6cdBlock suppression via NU5 same-header body poisoning of sent-hash cache · Advisory · ZcashFoundation/zebra · GitHub
https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-4m69-67m6-prqpVendor Advisories for CVE-2026-52736(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 / 15× 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 22:37 UTCEG score recompute
- 2026-08-24 10:16 UTCEG score recompute
- 2026-08-23 07:45 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 06:26 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:44 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 04:02 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 19:29 UTCEG score recompute▲ 8.70
- 2026-08-18 19:29 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
- 2026-08-02 00:43 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-52736?
When was CVE-2026-52736 disclosed?
Is CVE-2026-52736 actively exploited?
What is the CVSS score of CVE-2026-52736?
How do I remediate CVE-2026-52736?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52736
Is Your Infrastructure Affected by CVE-2026-52736?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.