CVE-2026-52737

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 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 4.5.0, a malicious unauthenticated P2P peer can answer Zebra's outbound getblocks or FindBlocks request with a small two-hash inventory and then serve a syntactically valid block whose coinbase height is far above the local chain tip. In zebrad/src/components/sync/downloads.rs, BlockDownloadVerifyError::AboveLookaheadHeightLimit originally carried only the block height and hash, so handle_block_response could not attribute the failure to the advertising peer. The error then reached the restart-worthy default path in zebrad/src/components/sync.rs, cancelling all in-flight downloads from honest peers and imposing a 67-second sync restart delay on mainnet. Because the peer was neither scored nor disconnected, the peer could repeat the cycle indefinitely with minimal bandwidth and significantly degrade synchronization without corrupting state. This issue is fixed in version 4.5.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 2, 2026

Last Modified

August 18, 2026

Advisory Details (5)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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

commit bc64dfe45746 (ZcashFoundation/zebra)

Fix landed in ZcashFoundation/zebra commit bc64dfe45746 — awaiting tagged release

https://github.com/ZcashFoundation/zebra/commit/bc64dfe45746a86d14546a0a5a766387dd5a2942
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
github_pr Patch Available

release: v4.5.0

Patch available: ZcashFoundation/zebra v4.5.0 (PR #10647 merged 2026-05-29)

https://github.com/ZcashFoundation/zebra/pull/10647
github Patch Available

Sync restart poisoning from single unauthenticated peer via above-lookahead block · Advisory · ZcashFoundation/zebra · GitHub

https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-gvjc-3w7c-92jx

Vendor Advisories for CVE-2026-52737(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 rangeFixed inDependents
zebra-consensus—7.0.0—
zebrad—4.5.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 12× 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-08-25 13:42 UTCEG score recompute
  2. 2026-08-24 11:18 UTCEG score recompute
  3. 2026-08-23 09:29 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 07:40 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 05:51 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 04:02 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 20:25 UTCEG score recompute
  12. 2026-07-30 23:33 UTCEG score recompute
  13. 2026-07-26 13:02 UTCEG score recompute
  14. 2026-07-23 03:19 UTCEG score recompute
  15. 2026-07-02 20:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52737?
CVE-2026-52737 is a medium vulnerability published on July 2, 2026. ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a malicious unauthenticated P2P peer can answer Zebra's outbound getblocks or FindBlocks request with a small two-hash inventory and then serve a syntactically valid block whose coinbase height is far above the local chain tip. In…
When was CVE-2026-52737 disclosed?
CVE-2026-52737 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52737 actively exploited?
CVE-2026-52737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.8% of all scored CVEs.
What is the CVSS score of CVE-2026-52737?
CVE-2026-52737 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-52737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52737, 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-52737

Explore →

Is Your Infrastructure Affected by CVE-2026-52737?

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

Start Free Scan →Browse All CVEs