CVE-2026-52739
MEDIUMDescription
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a malicious block producer can terminate zebrad by placing the same shielded transaction in a non-finalized parent block and its child. In zebra-state/src/service/non_finalized_state/chain.rs, Chain::push originally inserted the transaction hash into tx_loc_by_hash and asserted uniqueness before updating shielded data and running the duplicate Sprout, Sapling, or Orchard nullifier checks. The repeated transaction therefore reached the transactions must be unique within a single chain assertion before contextual validation could reject it cleanly. Zebra release builds use panic equals abort, so the reachable assertion terminates the entire process; exploitation requires either two consecutive attacker-mined blocks or an attacker-mined child immediately after an honest block includes the attacker's shielded transaction. 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
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-248 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-59538 | High | 7.5 | 8.3% | - | Fix |
| CVE-2021-37714 | High | 7.5 | 6.9% | - | Fix |
| CVE-2025-53366 | Unscored | - | 6.8% | - | - |
| CVE-2018-11466 | Critical | 9.8 | 4.0% | - | - |
| CVE-2025-59465 | High | 7.5 | 3.8% | - | Fix |
| CVE-2018-7852 | High | 7.5 | 3.6% | - | - |
Common questions
How do I fix CVE-2026-52739?
No published fix for CVE-2026-52739 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-52739 being actively exploited?
Not that we know of. CVE-2026-52739 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-52739?
CVE-2026-52739 has a CVSS v3 base score of 5.9, 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-52739
Markdown
[](https://tridentstack.com/cve/CVE-2026-52739)HTML
<a href="https://tridentstack.com/cve/CVE-2026-52739"><img src="https://tridentstack.com/cve/badge/CVE-2026-52739.svg" alt="CVE-2026-52739"></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.
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.