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-109366 Overview
CVE-2026-109366 is an improper integrity validation vulnerability [CWE-354] in Zebra, the Zcash Foundation's Rust implementation of a Zcash full node. Versions before 6.4.0 fail to validate block integrity in the inbound gossip download path. Unauthenticated network peers can force the node to drop valid new blocks without triggering any peer penalty. The flaw allows attackers to serve a real block whose coinbase scriptSig has been rewritten to height 1 while preserving the ZIP-244 block hash. This triggers a behind-tip drop before consensus validation, delaying tip discovery for mining backends that depend on Zebra.
Critical Impact
Remote unauthenticated attackers can delay block tip discovery on Zebra nodes, degrading mining backend availability without authentication or user interaction.
Affected Products
- Zcash Foundation Zebra full node versions prior to 6.4.0
- Mining backends relying on affected Zebra nodes for tip discovery
- Zcash network participants running vulnerable gossip-enabled peers
Discovery Timeline
- 2026-10-12 - CVE-2026-109366 published to the National Vulnerability Database
- 2026-10-12 - Last updated in NVD database
Technical Details for CVE-2026-109366
Vulnerability Analysis
The vulnerability resides in Zebra's inbound gossip download handling. When a peer gossips a new block, Zebra performs preliminary checks before full consensus validation. One of these checks compares the block's declared height against the node's current tip. The height comparison relies on the coinbase scriptSig encoded height rather than on consensus-verified state. An attacker rewrites the coinbase scriptSig to encode height 1 while leaving all other fields intact. Because the ZIP-244 block hash algorithm does not cover the mutable portion of the scriptSig used here, the forged block retains a valid hash. Zebra then classifies the block as behind-tip and silently drops it, with no misbehavior score applied to the sending peer.
Root Cause
The root cause is reliance on untrusted, pre-consensus data for an integrity decision. The gossip path trusts the coinbase-encoded height instead of deferring the drop decision until after consensus validation. CWE-354 (Improper Validation of Integrity Check Value) captures this pattern: an integrity-sensitive branch executes on data that has not been cryptographically bound to the block identity.
Attack Vector
Exploitation requires only network reachability to a target Zebra node. An attacker fetches a real, recently mined block from the Zcash network. The attacker rewrites the coinbase scriptSig height field to 1, re-serializes the block, and gossips it to the victim. Zebra computes the ZIP-244 hash, finds it matches the real block, then evaluates the forged height and classifies the block as stale. The block is dropped before consensus validation would have caught the tampering, and no peer penalty is recorded. Repeated delivery suppresses legitimate tip propagation to the node, delaying work updates for connected miners. Technical details are available in the GitHub Security Advisory and the VulnCheck Vulnerability Advisory.
Detection Methods for CVE-2026-109366
Indicators of Compromise
- Zebra log entries indicating repeated behind-tip block drops from the same or rotating peer addresses
- Mining backends reporting stale work templates or delayed getblocktemplate updates while the public network tip advances
- Inbound gossip messages containing coinbase scriptSig height values inconsistent with the block's expected chain position
Detection Strategies
- Monitor Zebra node metrics for divergence between the local tip height and the Zcash network tip height observed via independent nodes or block explorers
- Correlate peer gossip volume with block-drop counters to identify peers that consistently submit discarded blocks without penalty
- Alert on sustained lag between block arrival timestamps and mining job updates on connected backends
Monitoring Recommendations
- Export Zebra Prometheus metrics for inbound block processing outcomes and track behind-tip drop rates
- Capture packet traces on the Zcash P2P port for forensic review of coinbase scriptSig content when drops spike
- Compare block hashes accepted locally against public Zcash chain data to detect prolonged tip lag
How to Mitigate CVE-2026-109366
Immediate Actions Required
- Upgrade Zebra to version 6.4.0 or later on all nodes serving mining backends or public peers
- Restrict inbound peer connections to known or vetted peers where operationally feasible until the upgrade is applied
- Audit mining backend logs for stale work incidents coinciding with the vulnerable window
Patch Information
The Zcash Foundation addressed the issue in Zebra 6.4.0. The fix removes reliance on the untrusted coinbase scriptSig height for the pre-consensus behind-tip decision. Refer to the GitHub Security Advisory GHSA-4f6v-mj46-gxg3 for release notes and commit references.
Workarounds
- Reduce the inbound peer slot count and prefer outbound connections to trusted peers to limit attacker reach
- Deploy a secondary, independently monitored Zcash node to cross-check tip progression and alert on divergence
- Rate-limit or firewall inbound Zcash P2P traffic from untrusted networks until the patched release is deployed
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

