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-104428 Overview
CVE-2026-104428 is a denial-of-service vulnerability in zebra-rpc versions prior to 11.0.0, the Rust implementation of a Zcash full node maintained by the Zcash Foundation. The getblock JSON-RPC method panics when invoked with verbosity level 2 against a side-chain block. The side-chain block's -1 confirmations sentinel is converted to u32 with .expect(), which aborts the process on failure. Remote unauthenticated attackers can repeatedly issue this call, directly or through lightwalletd, to keep the node in a crash loop. The weakness is tracked as CWE-617: Reachable Assertion.
Critical Impact
Unauthenticated remote attackers can force Zebra nodes into a persistent crash loop, degrading Zcash network availability and lightwalletd-dependent wallet services.
Affected Products
- Zcash Foundation Zebra node (zebra-rpc crate) versions prior to 11.0.0
- Deployments exposing the getblock JSON-RPC method to untrusted callers
- lightwalletd instances backed by a vulnerable Zebra node
Discovery Timeline
- 2026-10-02 - CVE-2026-104428 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104428
Vulnerability Analysis
The flaw lives in the getblock RPC handler of zebra-rpc. When a client requests verbosity level 2, Zebra enriches the response with per-transaction details and includes a confirmations field. For blocks on the main chain, confirmations are a non-negative count. For side-chain blocks, Zebra uses -1 as a sentinel to signal that the block is not part of the best chain.
The handler then attempts to convert this signed value into an unsigned u32. The conversion is wrapped in .expect(), which panics when the source integer is negative. Because the Zebra node runs the RPC server within the same process as consensus and networking, the panic aborts the entire node rather than returning a structured RPC error.
An attacker only needs the hash of any side-chain block, which is observable on the public network, to trigger the condition. Each successful call terminates the process, and automated restart logic enables a sustained crash loop.
Root Cause
The root cause is unsafe handling of a known sentinel value. The code treats a logically valid -1 confirmations result as unreachable and uses .expect() instead of returning an RPC-level error. This matches CWE-617, a reachable assertion that aborts the process on attacker-influenced input.
Attack Vector
Exploitation is network-based, unauthenticated, and low-complexity. An attacker sends a JSON-RPC getblock request specifying a side-chain block hash and verbosity 2. If the Zebra RPC endpoint is reachable, directly or proxied through lightwalletd, the request forces the node to panic. Repeating the request keeps the node offline, affecting wallets, indexers, and services that depend on it. See the GitHub Security Advisory GHSA-x6v8-c2xp-928m and the VulnCheck Denial of Service Advisory for technical details.
Detection Methods for CVE-2026-104428
Indicators of Compromise
- Unexpected Zebra process termination correlated with inbound JSON-RPC traffic to the getblock method
- Panic messages in Zebra logs referencing u32 conversion from a negative value during getblock handling
- Repeated getblock requests with verbosity=2 targeting block hashes that are not on the best chain
- lightwalletd upstream errors indicating the backing Zebra node is unreachable or restarting
Detection Strategies
- Parse Zebra stderr and systemd journal entries for panicked at messages tied to the RPC worker and alert on recurrence
- Instrument the RPC reverse proxy to log method, params, and client IP, then flag getblock calls with verbosity 2 against non-best-chain hashes
- Correlate node restart events with inbound RPC spikes from the same source within a short time window
Monitoring Recommendations
- Track Zebra process uptime and restart counters, and alert when restarts exceed a baseline threshold
- Monitor RPC request rates per source IP and apply anomaly detection to getblock traffic
- Forward node and proxy logs to a centralized analytics platform to retain evidence of crash-loop activity
How to Mitigate CVE-2026-104428
Immediate Actions Required
- Upgrade zebra-rpc and the Zebra node to version 11.0.0 or later on all operators and infrastructure providers
- Restrict the Zebra JSON-RPC endpoint to trusted networks and authenticated clients using firewall rules or a reverse proxy
- Place lightwalletd and Zebra behind rate limiting that caps getblock request frequency per source
- Review logs for prior panics tied to getblock to identify opportunistic probing
Patch Information
The Zcash Foundation addressed the issue in Zebra 11.0.0 by handling the -1 confirmations sentinel without panicking. Operators should upgrade following the guidance in the GitHub Security Advisory GHSA-x6v8-c2xp-928m.
Workarounds
- Block or filter JSON-RPC getblock requests with verbosity=2 at an upstream proxy until the node is upgraded
- Disable public exposure of the Zebra RPC port and require VPN or mutual TLS access from lightwalletd and operators
- Deploy a supervisor that detects repeated panics and temporarily blackholes offending client IPs
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

