zebrad vulnerable to full node denial of service via crafted Sapling receiver in z_listunifiedreceivers

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Am I affected You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your zebrad.toml sets rpc.listenaddr to a TCP address (RPC server is enabled). 3. An attacker can authenticate to the RPC endpoint. With the default enablecookieauth = true, this requires the attacker to read the .cookie file (typically local access). With enablecookieauth = false, any network client reaching the RPC port can trigger it. Summary The zlistunifiedreceivers RPC handler panics when processing a structurally valid Unified Address whose Sapling receiver carries 43 bytes that fail cryptographic validation (saplingcrypto::PaymentAddress::frombytes returns None for non-subgroup Jubjub points). The handler calls .expect("using data already decoded as valid") on the fallible result. Because Zebra's release profile sets panic = "abort", the panic terminates the entire node process, not just the RPC task. Details zcashaddress::unified::Encoding::decode validates only the structural envelope of a…

Published by the source

2 Jul 2026, 19:37 UTC

Last modified by the source

2 Jul 2026, 19:38 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c8w6-x74f-vmg3

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

# Patch Next advisory brief: GHSA-c8w6-x74f-vmg3

Advisory: zebrad vulnerable to full node denial of service via crafted Sapling receiver in z_listunifiedreceivers
IDs: GHSA-c8w6-x74f-vmg3
Record: https://patchnext.com/advisories/ghsa-c8w6-x74f-vmg3 (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: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zebra-rpc 8.0.0; zebrad 4.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zebra-rpc: affected <= 7.0.0; fixed in 8.0.0
- crates.io zebrad: affected <= 4.4.1; fixed in 4.5.0

## Suggested inspection (read-only)
- crates.io zebra-rpc: 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-rpc, 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-c8w6-x74f-vmg3 (GitHub-reviewed advisory GHSA-c8w6-x74f-vmg3 lists affected ranges: crates.io zebra-rpc >=0 =0 <=4.4.1)

Commands are suggestions: review each one before running it.