CVE-2026-52738

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% 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, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

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 computed
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

Published

July 2, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)

Finalized address balance credit-first overflow on consensus-valid blocks · Advisory · ZcashFoundation/zebra · GitHub

https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-w834-cf6p-9m9w
github_release Patch Available

Zebra 4.5.0

Patch available: ZcashFoundation/zebra v4.5.0

https://github.com/ZcashFoundation/zebra/releases/tag/v4.5.0
github_commit Patch Available

commit 1440b43ca7df (ZcashFoundation/zebra)

Patch available: ZcashFoundation/zebra v4.5.0 (contains commit 1440b43ca7df)

https://github.com/ZcashFoundation/zebra/commit/1440b43ca7df59aca948090d45117557b217a6cd

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
zebrad—
  • every version up to 4.5.0: fixed in 4.5.0
—
zebra-state—
  • every version up to 7.0.0: fixed in 7.0.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-23 06:38 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 06:14 UTCEG score recompute
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-13 14:05 UTCEG score recompute
  25. 2026-09-12 14:15 UTCEG score recompute
Show 37 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-09 22:59 UTCEG score recompute
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 23:53 UTCEG score recompute
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 11:22 UTCEG score recompute
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 22:15 UTCEG score recompute
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 20:55 UTCEG score recompute
  21. 2026-08-23 19:14 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 19:24 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 17:15 UTCEG score recompute
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-20 16:16 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 16:26 UTCEG score recompute
  30. 2026-08-19 15:38 UTCEG score recompute
  31. 2026-08-18 20:25 UTCEG score recompute
  32. 2026-08-18 19:29 UTCEG score recompute▲ 6.90
  33. 2026-08-18 19:29 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  34. 2026-08-01 20:51 UTCEG score recompute
  35. 2026-07-26 13:02 UTCEG score recompute
  36. 2026-07-23 03:19 UTCEG score recompute
  37. 2026-07-02 20:07 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-52738?
CVE-2026-52738 is a medium vulnerability published on July 2, 2026. 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/finalizedstate/zebradb/transparent.rs, the finalized-state writer originally applied…
When was CVE-2026-52738 disclosed?
CVE-2026-52738 was first published on July 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52738 actively exploited?
CVE-2026-52738 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52738?
CVE-2026-52738 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52738?
A fix for CVE-2026-52738 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52738 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52738

Explore →

Is Your Infrastructure Affected by CVE-2026-52738?

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

Book a Demo →Browse All CVEs