CVE-2026-52737 ZEBRA: Sync restart poisoning from single unauthenticated peer via above-lookahead block

Medium 5.3 Published Updated

A malicious peer can repeatedly trigger sync restarts in Zebra nodes, causing significant synchronization delays and resource exhaustion.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-52737?

CVE-2026-52737 is a medium-severity denial of service vulnerability in ZcashFoundation zebra, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-345

Which versions are affected by CVE-2026-52737?

4 open source packages ship an affected version, including zebra-consensus and zebrad.

PackageAffectedFixed in
zebra-consensus crates.ioAll versions7.0.0
zebra-consensus crates.ioAll versions7.0.0
zebrad crates.ioAll versions4.5.0
zebrad crates.ioAll versions4.5.0

How do I fix CVE-2026-52737?

Upgrade zebra-consensus to 7.0.0 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-52737 being exploited?

There is no known exploitation of CVE-2026-52737 in the wild and no public exploit code.

Sources

Also known as GHSA-gvjc-3w7c-92jx.

Is CVE-2026-52737 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free