Saturday, November 21, 2026

Zebra 7.1.0 Fixes Ten Zcash Node Vulnerabilities

Neon cyberpunk Zebra Zcash node with shield, streaming blocks and memory flow, illustrating Zebra 7.1.0 security fixes.

The Zcash Foundation has released Zebra 7.1.0, a security-focused update addressing ten vulnerabilities across synchronization, memory management and transaction verification. According to the official Zcash Foundation release, operators running Zebra 7.0.0 can upgrade without migrating state or downloading the blockchain again. The release changes node implementation behavior without introducing a Zcash consensus change.

Several of the highest-priority issues allowed a remote peer to interfere with a node’s ability to synchronize. Forged blocks could halt initial sync at the transition from checkpoint verification to full validation, rewritten block data could prevent a node from progressing, and malicious responses containing already-known blocks could repeatedly restart sync rounds. Most of the security impact centers on availability and resource exhaustion rather than transaction validity or loss of funds. GitHub’s release record explicitly states that none of the ten advisories constitutes a consensus fault or directly puts user funds at risk.

Memory and Sync Attacks Drive Upgrade Priority

Two high-severity advisories specifically addressed memory exhaustion. In one case, unusually dense blocks containing transparent outputs could cause competing chain branches to duplicate recent-state indexes until the node exhausted available memory, potentially repeating after restart. Another flaw allowed concurrent transparent-address balance requests through getaddressbalance or lightwalletd to consume excessive memory. The second issue means exposure was not limited to hostile Zcash peers because clients accessing a public RPC or wallet service could also trigger resource pressure.

Zebra 7.1.0 now limits recent-state indexes and changes how competing branches share that data. On mainnet, those indexes are capped at 6.2 million entries, while Zebra continues to recommend 16 GB of RAM. The release also adds memory telemetry, sync-restart diagnostics and automatic peer recovery when a node loses all outbound connections. The mitigation combines vulnerability fixes with additional observability intended to make future synchronization failures easier to diagnose.

The remaining advisories include excessive verification work in the mempool and incorrect peer attribution. Zebra previously performed expensive signature or zero-knowledge proof work on some transactions before cheaper checks determined they should be rejected, while another issue could let a forged block supplied first cause an honest peer to be banned later. These bugs could consume node resources or degrade peer connectivity even when the blockchain’s consensus rules remained unaffected.

Security Release Follows Recent Zcash Upgrades

The patch arrives shortly after NU7 activated on Zcash mainnet, with Zebra 7.0.0 serving as the first stable client release supporting that network upgrade. The transition followed a series of infrastructure changes this year, including the earlier Zebra 4.5.3 and 5.0.0 emergency releases that addressed the Orchard soundness issue. Unlike those consensus-sensitive upgrades, Zebra 7.1.0 is an implementation security release and does not activate a new network rule.

The timing also creates a relatively short operational window. GitHub and non-crypto software release tracker NewReleases.io both list Zebra 7.1.0 as supported only until approximately December 10, when the client is expected to reach its built-in end-of-support halt. Operators will begin receiving warnings roughly a week earlier. Upgrading to 7.1.0 therefore fixes the current vulnerabilities, but operators will still need another client update before the December support cutoff.

That requirement is particularly relevant for miners, exchanges, wallet infrastructure and public lightwalletd services, all of which the Foundation places in the high-priority upgrade category. Current network infrastructure can also be tracked through ChainReport’s Zcash NU7 upgrade dashboard and Zebra node requirements overview. For production operators, the immediate security action is straightforward: move from Zebra 7.0.0 to 7.1.0 without a resync, then prepare for the next supported release before December 10.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.