Zebra 4.3.0 adds NSM (ZIP-235) support
Along with critical security fixes, support for the Network Sustainability Mechanism (ZIP-235) was added. The remote denial-of-service vulnerability was rated CVSS 9.2.
The Zcash Foundation released Zebra 4.3.0. The release contains critical security fixes, and it strongly urged all node operators to upgrade immediately. Along with the security patches, it introduces support for the Network Sustainability Mechanism (NSM, ZIP-235), improves performance-profiling developer tools and fixes several bugs.
There are two security advisories. CVE-2026-34202 (Critical, CVSS 9.2) lets a remote, unauthenticated attacker crash a node with a crafted V5 transaction that passes initial deserialization but causes a panic during transaction ID computation. CVE-2026-34377 (High, CVSS 8.4) is a logic error in the transaction verification cache that let a malicious miner insert incorrect authorization data matching a valid transaction's txid, which could induce a chain split. Invalid transactions are not accepted.
Two more issues were disclosed. One is a bug where a V5 transaction was treated as fully verified based only on its mined transaction ID, skipping proof verification. Because the transaction was valid, no invalid transaction was accepted, but if a transaction with an invalid proof were mined, a chain split with other implementations could occur. The other is a panic during deserialization of some transactions handled by librustzcash. They were responsibly reported by alexs-scalar and robustfengbin respectively, and the V5 transaction test generator was also extended to prevent recurrence.
The new feature is an initial implementation of ZIP-235; it is disabled by default and behind a feature flag, so it is not turned on in production builds and can be used only for testing and development. A Cargo profile and documentation for profiling were added. Bug fixes include Regtest block propagation, a missing Founders' Reward deduction in getblocksubsidy before Canopy, and a testnet performance problem where repeated checkpoint parsing kept one CPU thread busy.
This summary is based on the original; check the original for exact details.