# CVE-2026-41584: ZEBRA: rk Identity Point Panic in Transaction Verification

> An attacker can crash a Zebra node by sending a crafted transaction with an identity value in the rk field, causing a panic.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-452v-w3gx-72wg

## What is CVE-2026-41584?

CVE-2026-41584 is a critical denial of service vulnerability in ZcashFoundation zebra, published on 8 May 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 zebrad version 4.3.1 and prior to zebra-chain version 6.0.2, Orchard transactions contain a rk field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a "zero" value), however, the orchard crate which is used to verify Orchard proofs would panic when fed a rk with the identity value. Thus an attacker could send a crafted transaction that would make a Zebra node crash. This issue has been patched in zebrad version 4.3.1 and zebra-chain version 6.0.2.

Weakness: CWE-617 (Reachable Assertion)

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

4 open source packages ship an affected version, including zebra-chain and zebrad. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zebra-chain` | crates.io | All versions | 6.0.2 |
| `zebra-chain` | crates.io | All versions | 6.0.2 |
| `zebrad` | crates.io | All versions | 4.3.1 |
| `zebrad` | crates.io | All versions | 4.3.1 |

Products: Zfnd Zebra-Chain, Zfnd Zebrad.

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

Upgrade zebra-chain to 6.0.2 or later.

## Is CVE-2026-41584 being exploited?

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

## Other vulnerabilities in ZcashFoundation zebra

- [CVE-2026-44500](https://insights.sbomify.com/CVE-2026-44500/): ZEBRA: Allocation Amplification in Inbound Network Deserializers (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41584 is a critical denial of service vulnerability in ZcashFoundation zebra, published on 8 May 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-41584 in the wild and no public exploit code.

Affected packages and fixed versions:
- zebra-chain (crates.io): affected all versions; fixed in 6.0.2
- zebra-chain (crates.io): affected all versions; fixed in 6.0.2
- zebrad (crates.io): affected all versions; fixed in 4.3.1
- zebrad (crates.io): affected all versions; fixed in 4.3.1

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-41584/ (Markdown: https://insights.sbomify.com/CVE-2026-41584/index.md)
```

## Sources

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

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