CVE-2026-52736
HIGHDescription
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a remote unauthenticated P2P peer can stall a Zebra node by racing an invalid block body against the valid canonical body for the same block header hash. ZIP-244 permits the attacker to mutate coinbase scriptSig authentication data while retaining the transaction identifiers, merkle root, and block header hash, so the poisoned body fails later commitment validation but shares the canonical hash. In zebra-state/src/service.rs, queue_and_commit_to_non_finalized_state recorded the hash in non_finalized_block_write_sent_hashes before contextual validation completed and did not remove it when the write task rejected the body. When the honest body later arrived, the cached hash caused KnownBlock::WriteChannel duplicate handling to suppress it, leaving the node stuck one height behind until restart or reorganization. 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 v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 37% of all known CVEs.
References
Related Vulnerabilities
Other CWE-459 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-17090 | High | 7.5 | 82% | - | Fix |
| CVE-2021-39327 | Medium | 5.3 | 72% | - | - |
| CVE-2025-31650 | High | 7.5 | 60% | - | Fix |
| CVE-2022-1552 | High | 8.8 | 12% | - | Fix |
| CVE-2018-18924 | High | 8.8 | 9.5% | - | - |
| CVE-2022-21125 | Medium | 5.5 | 6.5% | - | Fix |
Common questions
How do I fix CVE-2026-52736?
No published fix for CVE-2026-52736 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-52736 being actively exploited?
Not that we know of. CVE-2026-52736 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.44% is the estimated probability that it will be exploited in the next 30 days. That is higher than 37% of all scored CVEs.
How severe is CVE-2026-52736?
CVE-2026-52736 has a CVSS v4 base score of 8.7, rated high. 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-52736
Markdown
[](https://tridentstack.com/cve/CVE-2026-52736)HTML
<a href="https://tridentstack.com/cve/CVE-2026-52736"><img src="https://tridentstack.com/cve/badge/CVE-2026-52736.svg" alt="CVE-2026-52736"></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-18.