CVE-2026-52829
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, an …
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, an unauthenticated IPv4 peer can deterministically terminate a synced Zebra node using the default Linux dual-stack listener configuration. The handshake path canonicalized an IPv4-mapped IPv6 PeerSocketAddr such as ::ffff:127.0.0.1 to plain IPv4 before storing it through MetaAddr::new_connected, but the mempool misbehavior path forwarded the raw transient address to MetaAddrChange::UpdateMisbehavior. In zebra-network/src/meta_addr.rs, apply_to_meta_addr then compared the canonical address-book entry with the raw update address and reached its unexpected address mismatch assertion. After the misbehavior batch flush, panic equals abort terminated zebrad; the peer only needed to complete a P2P handshake and advertise an invalid mempool transaction. This issue is fixed in version 4.5.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/ZcashFoundation/zebra/security/advisories/GHSA-63wg-wjjj-7cp8
- github.com/advisories/GHSA-63wg-wjjj-7cp8
- github.com/ZcashFoundation/zebra/commit/1440b43ca7df59aca948090d45117557b217a6cd
- github.com/ZcashFoundation/zebra/releases/tag/v4.5.0
- nvd.nist.gov/vuln/detail/CVE-2026-52829
- cve.org/CVERecord?id=CVE-2026-52829
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.