CVE & CISA-KEV Catalog

CVE-2026-52733

MEDIUM
6.5
CVSS v3
NVD

Description

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityHigh
AvailabilityLow

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L

Exploit Intelligence

0.34%probability of exploitation in 30 days
26thpercentile

Low risk: more likely to be exploited than 26% of all known CVEs.

References

Related Vulnerabilities

Other CWE-459 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2017-17090High7.582%-Fix
CVE-2021-39327Medium5.372%--
CVE-2025-31650High7.560%-Fix
CVE-2022-1552High8.812%-Fix
CVE-2018-18924High8.89.5%--
CVE-2022-21125Medium5.56.5%-Fix

Common questions

How do I fix CVE-2026-52733?

No published fix for CVE-2026-52733 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-52733 being actively exploited?

Not that we know of. CVE-2026-52733 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.34% is the estimated probability that it will be exploited in the next 30 days. That is higher than 26% of all scored CVEs.

How severe is CVE-2026-52733?

CVE-2026-52733 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-52733
CVE-2026-52733 severity badge

Markdown

[![CVE-2026-52733](https://tridentstack.com/cve/badge/CVE-2026-52733.svg)](https://tridentstack.com/cve/CVE-2026-52733)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-52733"><img src="https://tridentstack.com/cve/badge/CVE-2026-52733.svg" alt="CVE-2026-52733"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.