Zebra 4.5.0: security fixes and shielded mining
It contains security fixes including a critical P2SH sigop issue that could cause a consensus fork. A feature for mining to shielded addresses was also newly added.
The Zcash Foundation released Zebra 4.5.0. It is a release that fixes several security vulnerabilities, including one critical to consensus, and strongly recommends that all node operators upgrade immediately. There is no known workaround, and only upgrading ensures a node stays on the correct chain. Along with this, a feature for mining to shielded addresses was added.
The most important item is the critical-severity GHSA-gf9r-m956-97qx. Zebra's pure-Rust transparent script parser ended signature-operation (sigop) counting early when it met an inactive opcode inside a P2SH redeem script, undercounting against the 20,000-sigop block limit. As a result, it could accept blocks that zcashd rejects, a consensus mismatch that could lead to a chain split. At high severity are a SentHashes problem that blocks NU5 block retries (reported independently by nine people) and a problem where an address balance overflows on a consensus-valid block and permanently halts the node.
Medium and low severity items include a panic on an invalid Sapling receiver in z_listunifiedreceivers (reported independently by six people), a UTF-8 boundary panic in getblocktemplate's longpollid, a single unauthenticated peer monopolizing the mempool queue, subtree root corruption after a non-final chain fork, a mempool cancel_handles leak, sync restarts caused by a single peer, a panic on dual-stack IPv4-mapped addresses, buffer reservation before the handshake and locator CPU amplification. This release includes 13 security advisories in all.
New features are support for mining to shielded addresses under ZIP-213 and a startup warning when Linux TCP slow-start-after-idle is enabled. Other changes include caps that stop a peer-specified CompactSize from causing large memory allocations and adjustments to maximum allocation limits for block::Hash and others, and the network configuration was renamed to use [network.params] instead of testnet_parameters (the old form is still accepted).
This release reflects the results of more than 80 security reports received through the ZCG vulnerability disclosure initiative (April-May 2026). The Foundation thanked the researchers who reported and the Least Authority team that carried out the AI-assisted audit, and noted that the duplicate reports confirmed the severity and breadth of the vulnerability classes.
This summary is based on the original; check the original for exact details.