Categories
CVE-2026-41584 high CVSS 7.5

Vulnerability in zebrad (CVE-2026-41584)

Summary

Vulnerability in zebrad (CVE-2026-41584). Risk of unauthorized operations or information disclosure. Exploitable via orchard. Mitigation: upgrade to 4.3.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41584 has been found in zebrad.
Attackers can target a specific entry point like orchard over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade zebrad to 4.3.1 or later.
If unsure, ask your IT team or search "zebrad CVE-2026-41584" on the vendor's site.

CVE-2026-41584 (zebrad) — CWE-617 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: orchard / circuits.rs / zcashd
Patched: 4.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-617) exists in zebrad. Attackers reach the vulnerable code path via orchard without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of zebrad. Attack surface: orchard / circuits.rs / zcashd.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.3.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zebrad' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'zebrad' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で zebrad を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade zebrad to 4.3.1

    ステージング環境で 4.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust zebrad
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.1"}]}]
rust zebra-chain
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.2"}]}]
crates.io zebrad
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.3.1"}]}]
crates.io zebra-chain
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.0.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details