dbcve.org
Zebra ChainApplication · Zfnd

CVE-2026-41584

HIGH · 7.5 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 4.3.1 / 6.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In ZEBRA (Zcash node in Rust), the Orchard transaction verification code would panic when processing a 'rk' field containing the identity value (zero point on the elliptic curve). Although the Zcash specification permits this value, the orchard crate could not handle it, allowing attackers to crash nodes via crafted transactions.

MitigationUpgrade zebrad to version 4.3.1 or later, or zebra-chain to version 6.0.2 or later, to obtain the patch that handles identity values correctly in the Orchard verification logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zebra ChainApplication
Affected:< 6.0.2
ZebradApplication
Affected:< 4.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check zebrad version
    Run `zebrad --version` or check the version of the zebrad binary in your deployment
    Affected if Version is less than 4.3.1
  2. Check zebra-chain library version
    Inspect the Cargo.lock file or dependencies for the zebra-chain crate version, or query the running node's reported version if available
    Affected if Version is less than 6.0.2
  3. Verify node is processing Zcash transactions
    Check node logs or status for incoming transaction processing activity
    Affected if Node is actively processing Zcash transactions and version is vulnerable
  4. Confirm Orchard protocol is active
    Inspect node configuration for Orchard-related settings or Zcash consensus branch activity
    Affected if Orchard transactions are being processed and version is vulnerable

You are affected if your zebrad version is below 4.3.1 or zebra-chain version is below 6.0.2, and your node is actively processing Zcash transactions with Orchard support enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.3.1 / 6.0.2 or later
Fixed in 4.3.16.0.2
Interim mitigation

Upgrade zebrad to version 4.3.1 or later, or zebra-chain to version 6.0.2 or later, to obtain the patch that handles identity values correctly in the Orchard verification logic.

Recommended fix High confidence

zebrad >= 4.3.1 OR zebra-chain >= 6.0.2

  1. Identify which Zebra component you are running: zebrad (the Zebra node binary) or zebra-chain (the Rust library used by zebrad)
  2. Check your current version by running 'zebrad -V' for zebrad, or checking your Cargo.lock for zebra-chain
  3. If running zebrad, upgrade to version 4.3.1 or later by updating your Cargo.toml dependency or downloading the new release binary
  4. If using zebra-chain as a dependency, update the version in your Cargo.toml to 6.0.2 or later (e.g., zebra-chain = "6.0.2")
  5. Rebuild your project to pull in the fixed version
  6. Restart the Zebra node service to apply the fix
  7. Verify the upgrade was successful by checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zebra Chain Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41584 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data