Skip to main content
Vulnerability Database/CVE-2026-104436

CVE-2026-104436: Zebra P2P Denial of Service Vulnerability

CVE-2026-104436 is a resource exhaustion flaw in Zebra that enables remote peers to overwhelm blocking-pool threads via oversized block locator vectors. This article covers technical details, affected versions, and mitigation.

Published:

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-104436 Overview

CVE-2026-104436 is an uncontrolled resource consumption vulnerability [CWE-770] affecting Zebra, the Rust implementation of a Zcash full node maintained by the Zcash Foundation. Versions prior to 4.5.0 fail to cap the number of hashes accepted in getblocks and getheaders peer-to-peer (P2P) messages. Remote peers can supply up to 65,535 locator hashes per message, forcing per-hash chain lookups on a blocking thread pool. The resulting CPU amplification degrades block validation, remote procedure call (RPC) responsiveness, and mempool performance on the targeted node.

Critical Impact

Unauthenticated remote P2P peers can exhaust Zebra's blocking-pool threads and reduce node availability without authentication or user interaction.

Affected Products

  • Zebra (Zcash Foundation full node) versions prior to 4.5.0
  • Deployments exposing the Zcash P2P port to untrusted peers
  • Downstream services relying on Zebra RPC or mempool availability

Discovery Timeline

  • 2026-10-02 - CVE-2026-104436 published to the National Vulnerability Database (NVD)
  • 2026-10-02 - Last updated in NVD database

Technical Details for CVE-2026-104436

Vulnerability Analysis

Zebra participates in the Zcash P2P protocol, which allows peers to request chain data using getblocks and getheaders messages. Each message carries a block locator: an ordered vector of block hashes used by the responding node to determine the fork point between peers. Zebra does not enforce an upper bound on the locator length beyond the protocol limit of 65,535 entries.

For each hash supplied, Zebra performs a chain lookup against its state service. These lookups run on a bounded blocking thread pool shared with block validation, mempool processing, and RPC handlers. A single peer sending maximum-length locators repeatedly can saturate that pool. The impact is loss of availability rather than data compromise, which aligns with the CWE-770 classification of uncontrolled resource allocation.

Root Cause

The root cause is missing input length validation on inbound locator vectors in the P2P message handlers. The code path accepts the protocol-maximum vector size and dispatches a chain lookup per element without rate limiting or short-circuit evaluation once a common ancestor is found cheaply.

Attack Vector

The attack is network-based and requires no authentication. An attacker peers with the target Zebra node over the standard Zcash P2P port and sends crafted getblocks or getheaders messages containing tens of thousands of locator hashes. Repeated requests, optionally from multiple peer connections, amplify CPU and thread-pool consumption. See the GitHub Security Advisory GHSA-443g-gwgp-49x4 and the VulnCheck Advisory on Zebra CPU amplification for protocol-level details.

Detection Methods for CVE-2026-104436

Indicators of Compromise

  • Inbound getblocks or getheaders messages containing locator vectors approaching 65,535 hashes from a single peer.
  • Sustained saturation of Zebra's blocking thread pool coinciding with elevated P2P ingress traffic.
  • Growth in RPC latency and mempool processing delays without a corresponding increase in legitimate chain activity.

Detection Strategies

  • Instrument Zebra with metrics on P2P message sizes and locator vector lengths, alerting when values exceed a reasonable threshold such as 500 hashes.
  • Correlate CPU spikes on the Zebra process with per-peer message rates to identify abusive peers.
  • Review peer connection logs for repeated short-lived sessions that issue large getblocks or getheaders requests.

Monitoring Recommendations

  • Export Zebra Prometheus metrics covering thread-pool queue depth, RPC latency, and peer message counters.
  • Baseline normal getblocks and getheaders request volumes and alert on sustained deviations.
  • Monitor upstream network devices for asymmetric traffic patterns characteristic of CPU amplification attacks.

How to Mitigate CVE-2026-104436

Immediate Actions Required

  • Upgrade Zebra to version 4.5.0 or later, which enforces a bounded locator length.
  • Restrict inbound P2P connectivity to known peers where operationally feasible until the upgrade is complete.
  • Enable per-peer rate limiting at the network edge to blunt sustained request floods.

Patch Information

The Zcash Foundation addressed CVE-2026-104436 in Zebra 4.5.0 by capping the number of locator hashes processed per getblocks and getheaders message. Operators should review the GitHub Security Advisory GHSA-443g-gwgp-49x4 for the fix commit and upgrade guidance.

Workarounds

  • Place Zebra behind a reverse proxy or firewall that drops oversized P2P messages before they reach the node.
  • Reduce the maximum inbound peer count to limit the number of concurrent abusive connections.
  • Isolate RPC consumers from the P2P-facing node by running a dedicated internal Zebra instance for RPC traffic.
bash
# Configuration example: restrict inbound peers and bind P2P to a trusted interface
# zebrad.toml
[network]
listen_addr = "10.0.0.5:8233"
peerset_initial_target_size = 25
# Firewall rule to allow only known peers on the P2P port
# iptables -A INPUT -p tcp --dport 8233 -s <trusted_peer_ip> -j ACCEPT
# iptables -A INPUT -p tcp --dport 8233 -j DROP

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.