CVE-2026-52737 is a medium-severity (CVSS 5.3) CWE-345 vulnerability in zebra-consensus. A fix is available for zebra-consensus — see the affected versions and patch details below.
ZEBRA: Sync restart poisoning from single unauthenticated peer via above-lookahead block
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-52737.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-52737 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
zebra-consensus🦀zebradReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Am I affected
You are affected if:
- You run
zebradup to and includingv4.4.1. - Your node accepts inbound P2P connections and is syncing or catching up to the chain tip.
Summary
A malicious peer can answer Zebra's outbound getblocks/FindBlocks request with a small two-hash inventory, then serve a syntactically valid block whose coinbase height is far above the victim's local tip. The AboveLookaheadHeightLimit error in the sync download pipeline triggers a global sync restart rather than being scoped to the offending peer. The peer is never scored or disconnected because the error type does not carry the advertiser address.
On mainnet, each successful cycle imposes a 67-second sync restart delay. All in-flight downloads from honest peers are cancelled on each restart.
Details
The bug is the interaction of three layers:
-
The syncer promotes unvalidated
FindBlockspeer responses into concrete download schedules without checking that the advertised hashes are plausible chain extensions. -
When a downloaded block's coinbase height exceeds
tip + VERIFICATION_PIPELINE_DROP_LIMIT, the sync downloader returnsBlockDownloadVerifyError::AboveLookaheadHeightLimit. This error variant carries only the block height and hash, not the advertiser peer address. -
The sync error handler in
handle_block_responseonly sends misbehaviour scores forBlockDownloadVerifyError::Invaliderrors that carry anadvertiser_addrand have a nonzeromisbehavior_score().AboveLookaheadHeightLimitfalls through to the default restart-worthy path, cancelling all in-flight downloads and waiting 67 seconds before restarting sync.
The attacker needs only an unauthenticated P2P connection (post-handshake), a tiny payload (one two-hash inv message plus one small block per cycle), and no mining capability, funds, or valid chain data. The peer is never penalised, so the attack is repeatable indefinitely.
Additionally, several other pre-consensus sync-layer errors had zero misbehaviour scores even when peer-attributed. Contextual validation failures (InvalidDifficultyThreshold, TimeTooEarly, TimeTooLate, NonSequentialBlock) and locktime failures from block-serving peers all scored zero, allowing repeated abuse without penalty.
Patches
Patched in Zebra 4.4.2. The fix:
- Carries
advertiser_addrthroughAboveLookaheadHeightLimitandInvalidHeighterror variants. - Makes above-lookahead and invalid-height failures peer-local (the block is dropped and the peer is banned with score 100) rather than triggering a global sync restart.
- Expands
misbehavior_score()acrossBlockError,VerifyBlockError, andCommitBlockErrorto cover contextual validation failures that previously scored zero.
Workarounds
No configuration-level workaround is available. The attack is mitigated by having a diverse honest peer set, but cannot be prevented while the vulnerable code is running.
Impact
A single unauthenticated peer can repeatedly stall a syncing Zebra node by forcing 67-second global sync restart cycles. All unrelated in-flight downloads are cancelled on each restart. The node does not crash and no state is corrupted, but sync progress is significantly degraded for the duration of the attack.
Credit
Reported by @ipwning.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | zebra-consensus | all versions | 7.0.0cargo update -p zebra-consensus --precise 7.0.0 |
| 🦀crates.io | zebrad | all versions | 4.5.0cargo update -p zebrad --precise 4.5.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zebra-consensus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zebra-consensus to 7.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-52737 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-52737 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-52737. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-52737 in your dependencies?
O3 Security finds CVE-2026-52737 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.