ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a consensus-valid block containing a long chain of transparent self-spends to one address can permanently halt Zebra nodes. In zebra-state/src/service/finalized_state/zebra_db/transparent.rs, the finalized-state writer originally applied every newly created output as a credit before applying any spent-output debit from the same block. That credit-first ordering can make the intermediate per-address balance exceed MAX_MONEY even though the final net balance is valid, causing an expect-based panic under the panic equals abort release profile. Because zcashd accepts the triggering block and Zebra encounters it again after every restart, the halt persists until patched software is deployed; exploitation requires mining the specially constructed block and temporarily committing sufficient ZEC to the self-spend chain. This issue is fixed in version 4.5.0.
CVE-2026-52738
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity69% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 19, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026Finalized address balance credit-first overflow on consensus-valid blocks · Advisory · ZcashFoundation/zebra · GitHub
https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-w834-cf6p-9m9wZebra 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-52738(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 12× in last 7d / 16× 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 20:55 UTCEG score recompute
- 2026-08-23 19:14 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:24 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 17:15 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 16:16 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:26 UTCEG score recompute
- 2026-08-19 15:38 UTCEG score recompute
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 19:29 UTCEG score recompute▲ 6.90
- 2026-08-18 19:29 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
- 2026-08-01 20:51 UTCEG score recompute
- 2026-07-26 13:02 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-52738?
When was CVE-2026-52738 disclosed?
Is CVE-2026-52738 actively exploited?
What is the CVSS score of CVE-2026-52738?
How do I remediate CVE-2026-52738?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52738
Is Your Infrastructure Affected by CVE-2026-52738?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.