CVE-2026-52733 ZcashFoundation CVE debrief

Who should care

Defenders responsible for ZEBRA node configuration and maintenance should assess exposure and prioritize updating to version 4.5.0. Defenders should verify and update their ZEBRA node to version 4.5.0 to prevent potential wallet synchronization failures or incorrect wallet state due to stale subtree roots. Operators of ZEBRA nodes should review node configuration and ensure proper cleanup of subtree entries.

Why it matters

Defenders should prioritize verifying and updating their ZEBRA node to version 4.5.0 to prevent potential wallet synchronization failures or incorrect wallet state due to stale subtree roots.

• Verification of node version and potential update to 4.5.0 is required to prevent stale subtree roots.
• Node restarts may be necessary to ensure consistency of subtree data.
• Wallet synchronization failures or incorrect wallet state may occur if subtree data is corrupted.

Technical summary

The Chain::pop_tip function in zebra-state/src/service/non_finalized_state/chain.rs did not properly remove subtree entries when a reverted tip block was removed, allowing stale subtree data to persist in RocksDB and potentially cause wallet synchronization failures or incorrect wallet state. The vulnerability can be fixed by updating to version 4.5.0. Defenders should prioritize verifying their ZEBRA node version and updating to 4.5.0 if necessary. The issue requires verification of node version and potential update to 4.5.0 to prevent stale subtree roots.

Defensive priority

Defenders should prioritize verifying their ZEBRA node version and updating to 4.5.0 if necessary.

Recommended defensive actions

• Verify ZEBRA node version and update to 4.5.0 if necessary
• Review node configuration and ensure proper cleanup of subtree entries
• Monitor node restarts and subtree data consistency
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but its exploitation and impact require verification. The issue is caused by the Chain::pop_tip function in zebra-state/src/service/non_finalized_state/chain.rs not properly removing subtree entries when a reverted tip block was removed. This allows stale subtree data to persist in RocksDB and potentially cause wallet synchronization failures or incorrect wallet state. Defenders should verify and update their ZEBRA node to version 4.5.0 to prevent potential issues.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.