Zebra has rk Identity Point Panic in Transaction Verification

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-41584: 0.27% estimated exploitation activity in the next 30 days; percentile 19.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

rk Identity Point Panic in Transaction Verification Summary 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. Severity Critical - This is a Denial of Service Vulnerability that could allow an attacker to crash Zebra nodes. Affected Versions All Zebra versions prior to version 4.3.1. Description The vulnerability exists in the circuits.rs file of the orchard crate; it attempts to get the coordinates of the rk value and calls unwrap() on the results, which causes a panic if rk is the identity. Zebra parses rk as a byte vector; it creates an Orchard "bundle" using the orchard crate and then calls the same crate to verify it, triggering the panic. An…

Published by the source

18 Apr 2026, 01:14 UTC

Last modified by the source

12 May 2026, 13:33 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-452v-w3gx-72wg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41584

Advisory: Zebra has rk Identity Point Panic in Transaction Verification
IDs: CVE-2026-41584, GHSA-452v-w3gx-72wg
Record: https://patchnext.com/advisories/cve-2026-41584 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zebra-chain 6.0.2; zebrad 4.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zebra-chain: affected < 6.0.2; fixed in 6.0.2
- crates.io zebrad: affected < 4.3.1; fixed in 4.3.1

## Suggested inspection (read-only)
- crates.io zebra-chain: check the installed version with your package manager.
- crates.io zebrad: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zebra-chain, zebrad.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-452v-w3gx-72wg (GitHub-reviewed advisory GHSA-452v-w3gx-72wg lists affected ranges: crates.io zebrad >=0 =0 <6.0.2)

Commands are suggestions: review each one before running it.