# CVE-2026-52736: ZEBRA: Block suppression via NU5 same-header body poisoning of sent-hash cache

> A remote attacker can stall a Zcash node by racing invalid block bodies against valid ones, causing the node to reject honest blocks and halt synchronization.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-4m69-67m6-prqp

## What is CVE-2026-52736?

CVE-2026-52736 is a high-severity vulnerability in ZcashFoundation zebra, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2026-52736?

4 open source packages ship an affected version, including zebra-state and zebrad.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zebra-state` | crates.io | All versions | 7.0.0 |
| `zebra-state` | crates.io | All versions | 7.0.0 |
| `zebrad` | crates.io | All versions | 4.5.0 |
| `zebrad` | crates.io | All versions | 4.5.0 |

## How do I fix CVE-2026-52736?

Upgrade zebra-state to 7.0.0 or later.

## Is CVE-2026-52736 being exploited?

There is no known exploitation of CVE-2026-52736 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52736 and fix it if it is affected.

What it is: CVE-2026-52736 is a high-severity vulnerability in ZcashFoundation zebra, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52736 in the wild and no public exploit code.

Affected packages and fixed versions:
- zebra-state (crates.io): affected all versions; fixed in 7.0.0
- zebra-state (crates.io): affected all versions; fixed in 7.0.0
- zebrad (crates.io): affected all versions; fixed in 4.5.0
- zebrad (crates.io): affected all versions; fixed in 4.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52736/ (Markdown: https://insights.sbomify.com/CVE-2026-52736/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52736
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52736
- OSV: https://osv.dev/vulnerability/CVE-2026-52736

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52736/
Summaries are generated and may contain mistakes; the official description above is the record.