CVE-2026-52733
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a …
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a natural or attacker-influenced chain fork can leave stale Sapling and Orchard note-commitment subtree roots in Zebra state. In zebra-state/src/service/non_finalized_state/chain.rs, Chain::pop_tip removed a reverted tip block but did not remove subtree entries whose end_height belonged to that block, unlike the cleanup performed by pop_root. When the winning fork later finalized, the abandoned branch's stale subtree data could be written to RocksDB and survive node restarts. The corrupted history can cause z_getsubtreesbyindex consumers such as lightwalletd and light wallets to receive incorrect subtree roots, producing wallet synchronization failures or incorrect wallet state and requiring a full state rebuild for recovery. 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-2gf8-q9rr-jq3h
- github.com/advisories/GHSA-2gf8-q9rr-jq3h
- github.com/ZcashFoundation/zebra/commit/1440b43ca7df59aca948090d45117557b217a6cd
- github.com/ZcashFoundation/zebra/releases/tag/v4.5.0
- nvd.nist.gov/vuln/detail/CVE-2026-52733
- cve.org/CVERecord?id=CVE-2026-52733
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.