Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104424 Overview
CVE-2026-104424 is an incorrect calculation vulnerability [CWE-131] in Zebra, the Rust implementation of a Zcash node maintained by the Zcash Foundation. Versions before 6.1.0 miscalculate block size inside the ZIP-317 block template selector used by getblocktemplate. The selector omits the block header and transaction-count fields from the budget, so templates can exceed the protocol size limit. An attacker can seed valid, selectable transactions into a victim miner's mempool and shape templates into oversized blocks that the network rejects, wasting proof-of-work on the mined candidates.
Critical Impact
Remote attackers can force Zcash miners running vulnerable Zebra nodes to produce rejected blocks, resulting in wasted hashpower and lost mining revenue.
Affected Products
- Zebra (Zcash Foundation Rust node) versions prior to 6.1.0
- Mining deployments relying on the Zebra getblocktemplate RPC
- Downstream services that construct Zcash block templates via Zebra
Discovery Timeline
- 2026-10-02 - CVE-2026-104424 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104424
Vulnerability Analysis
The flaw lives in Zebra's ZIP-317 block template selector, the component responsible for picking which mempool transactions to include when a miner calls getblocktemplate. The selector tracks a running size budget that must stay under the Zcash block size limit. The calculation only accounts for serialized transaction bytes and ignores the fixed-size block header and the variable-length transaction count prefix. As a result, the budget overestimates available space.
When a miner assembles the final block from the returned template, the serialized block exceeds the protocol maximum. The network rejects the submitted block during propagation and validation. Any proof-of-work spent on that candidate is discarded.
Root Cause
The root cause is an incorrect size calculation [CWE-131] where the block budget excludes mandatory structural fields. The ZIP-317 selector treats the budget as equal to the raw transaction payload size, rather than the total serialized block size. This mismatch between accounting and actual on-wire size allows templates to grow past the hard limit without triggering internal guards.
Attack Vector
The attack is remote and unauthenticated. An attacker broadcasts valid, fee-paying transactions sized to be selectable under ZIP-317 priority rules. These transactions enter the victim miner's mempool through normal peer-to-peer propagation. On the next getblocktemplate call, the selector packs enough of these transactions to push the final block beyond the size limit. The miner mines the oversized candidate, submits it, and the network rejects it. No credentials, user interaction, or custom protocol access is required. Impact is limited to availability of mining output; consensus integrity and user funds are not affected.
No verified public exploit code is available at this time. See the GitHub Security Advisory GHSA-95m2-vx53-v2jw and the VulnCheck advisory for additional technical detail.
Detection Methods for CVE-2026-104424
Indicators of Compromise
- Repeated submitblock failures or block rejection errors in Zebra logs referencing oversized blocks
- Mined blocks that fail propagation with size-limit validation errors from peers
- Unexplained drops in effective mining yield despite stable hashrate
- Mempool entries containing clusters of similarly sized, selectable transactions from unfamiliar sources
Detection Strategies
- Compare the serialized size of templates returned by getblocktemplate against the Zcash block size limit before submission
- Alert on any submitblock RPC result that reports a size or weight violation
- Monitor the Zebra version string reported by the node and flag any instance running a release earlier than 6.1.0
Monitoring Recommendations
- Centralize Zebra node logs and parse for template construction and block rejection events
- Track per-template transaction count and total serialized size as time-series metrics
- Watch mempool inflow for sudden spikes of selectable transactions preceding template generation
How to Mitigate CVE-2026-104424
Immediate Actions Required
- Upgrade all Zebra nodes used for mining or template generation to version 6.1.0 or later
- Audit mining pool infrastructure to confirm no legacy Zebra builds remain in rotation
- Validate serialized block size against the protocol limit before calling submitblock as a defensive check
Patch Information
The Zcash Foundation addressed the issue in Zebra 6.1.0. The fix corrects the ZIP-317 selector so that the budget accounts for the block header and transaction count prefix in addition to transaction bytes. Full release details are available in the GitHub Security Advisory GHSA-95m2-vx53-v2jw.
Workarounds
- Restrict getblocktemplate RPC access to trusted mining clients using authenticated transports
- Apply conservative upper bounds on template transaction counts in operator tooling until the patch is deployed
- Reject locally any assembled block whose serialized size approaches the protocol maximum
# Verify installed Zebra version and upgrade path
zebrad --version
# After upgrade, confirm version is 6.1.0 or later
zebrad --version | grep -E 'zebrad 6\.(1|[2-9])'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

