CVE-2026-52736
Zebra Zcash nodes (<4.5.0) can be stalled by a malformed block-body race causing node lag.
Is CVE-2026-52736 being exploited?
Not confirmed. CVE-2026-52736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-52736?
CVE-2026-52736 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-52736?
Yes. A fix has been recorded for CVE-2026-52736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-52736 affect?
CVE-2026-52736 affects Zebra (Zcash node) < 4.5.0, Zcash nodes running Zebra. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-52736?
Upgrade Zebra to v4.5.0 immediately; restart nodes if already stalled.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated P2P peer can stall a Zebra node (DoS), suppressing valid block delivery and leaving node one height behind until restart/reorg.
Patch when possible
- affected< 4.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.