CVE-2026-34202: Zebrad Zebra Node Crash — V5 Vulnerability

CRITICAL
Advisory Identifier: GHSA-qp6f-w4r3-h8wg
CWE-94 CWE-1336
Published
Advisory Summary

CVE-2026-34202 is a CRITICAL zebra node crash — v5 vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Zebrad libraries in the crates.io ecosystem. The issue involves zebra node crash — v5 transaction hash panic (p2p reachable). Remediation is available by upgrading affected packages to version 4.3.0, 6.0.1.

CVE-2026-34202 at a Glance

CVE Identifier CVE-2026-34202
GHSA Identifier GHSA-qp6f-w4r3-h8wg
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Zebrad
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-34202

To remediate this vulnerability, upgrade all affected Zebrad dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

zebrad fixed: 4.3.0
Upgrade zebrad to 4.3.0
zebra-chain fixed: 6.0.1
Upgrade zebra-chain to 6.0.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for zebrad

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34202, inspect your project dependencies for Zebrad:

inspect dependencies for zebrad

Analyze the terminal output to locate any version of Zebrad in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.3.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Zebrad, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

--- # Remote Denial of Service via Crafted V5 Transactions ## Summary A vulnerability in Zebra's transaction processing logic allows a remote, unauthenticated attacker to cause a Zebra node to panic (crash). This is triggered by sending a specially crafted V5 transaction that passes initial deserialization but fails during transaction ID calculation. ## Severity **Critical** - This is a Remote Denial of Service (DoS) that requires no authentication and can be triggered by a single network message. ## Affected Versions All Zebra versions supporting V5 transactions (Network Upgrade 5 and later) prior to **version 4.3.0**. ## Description The vulnerability stems from Zebra lazily validating transaction fields that are eagerly validated in the librustzcash parsing logic used when Zebra computes transaction ids and auth digests for V5 transactions where Zebra panics if those computations fail. `PushTransaction` messages with malformed V5 transactions are successfully deserialized as the zebra-chain `Transaction` type by the network codec, but when Zebra converts those transactions into internal types to compute the TxID expecting it to succeed, it triggers a panic/crash. An attacker can trigger this crash by sending a single crafted `tx` message to a Zebra node's public P2P port. The same issue can be triggered via the `sendrawtransaction` RPC method. ## Impact **Remote Denial of Service** * **Attack Vector:** Remote, unauthenticated. * **Effect:** Immediate crash of the Zebra node. * **Scope:** Any node with an open P2P port (default 8233) or exposed RPC interface is vulnerable. ## Fixed Versions This issue is fixed in **Zebra 4.3.0**. The fix ensures that any transaction that would fail TxID calculation is rejected during the initial deserialization phase, and replaces internal panics with graceful error handling. ## Mitigation Users should upgrade to **Zebra 4.3.0** or later immediately. If an immediate upgrade is not possible, users should ensure their RPC port is not exposed to the Internet. However, the P2P port must remain closed or restricted to trusted peers to fully mitigate the risk, which may impact the node's ability to sync with the network. ## Credits Zebra thanks [robustfengbin](https://github.com/robustfengbin), who discovered this issue and reported it via coordinated disclosure process. ---

CVE-2026-34202 Affected Zebrad Versions

2 component(s)
Fixed Versions:
4.3.06.0.1
Product / Package Ecosystem Affected Versions Fixed Version
zebrad
crates.io
< 4.3.0
4.3.0
zebra-chain
crates.io
< 6.0.1
6.0.1

References

Frequently Asked Questions

What is CVE-2026-34202?
CVE-2026-34202 is a security vulnerability in Zebrad involving Zebra node crash — V5 transaction hash panic (P2P reachable) under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Zebrad versions are affected?
Affected versions include releases prior to 4.3.0, 6.0.1 across affected packages: zebrad, zebra-chain.
What version fixes CVE-2026-34202?
Upgrading to 4.3.0, 6.0.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is zebrad affected?
Yes, zebrad is affected in releases prior to 4.3.0. Upgrade your dependency to 4.3.0 or later.
Is zebra-chain affected?
Yes, zebra-chain is affected in releases prior to 6.0.1. Upgrade your dependency to 6.0.1 or later.
What CWE is associated with CVE-2026-34202?
CVE-2026-34202 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check crates.io dependencies for CVE-2026-34202?
Run the dependency tree command: 'inspect dependencies for zebrad'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qp6f-w4r3-h8wg",
  "modified" : "2026-03-31T18:50:56Z",
  "published" : "2026-03-27T22:19:24Z",
  "aliases" : [ "CVE-2026-34202" ],
  "summary" : "Zebra node crash — V5 transaction hash panic (P2P reachable)",
  "details" : "---\n\n# Remote Denial of Service via Crafted V5 Transactions\n\n## Summary\nA vulnerability in Zebra's transaction processing logic allows a remote, unauthenticated attacker to cause a Zebra node to panic (crash). This is triggered by sending a specially crafted V5 transaction that passes initial deserialization but fails during transaction ID calculation.\n\n## Severity\n**Critical** - This is a Remote Denial of Service (DoS) that requires no authentication and can be triggered by a single network message.\n\n## Affected Versions\nAll Zebra versions supporting V5 transactions (Network Upgrade 5 and later) prior to **version 4.3.0**.\n\n## Description\nThe vulnerability stems from Zebra lazily validating transaction fields that are eagerly validated in the librustzcash parsing logic used when Zebra computes transaction ids and auth digests for V5 transactions where Zebra panics if those computations fail.\n\n`PushTransaction` messages with malformed V5 transactions are successfully deserialized as the zebra-chain `Transaction` type by the network codec, but when Zebra converts those transactions into internal types to compute the TxID expecting it to succeed, it triggers a panic/crash.\n\nAn attacker can trigger this crash by sending a single crafted `tx` message to a Zebra node's public P2P port. The same issue can be triggered via the `sendrawtransaction` RPC method.\n\n## Impact\n**Remote Denial of Service**\n* **Attack Vector:** Remote, unauthenticated.\n* **Effect:** Immediate crash of the Zebra node.\n* **Scope:** Any node with an open P2P port (default 8233) or exposed RPC interface is vulnerable.\n\n## Fixed Versions\nThis issue is fixed in **Zebra 4.3.0**. \n\nThe fix ensures that any transaction that would fail TxID calculation is rejected during the initial deserialization phase, and replaces internal panics with graceful error handling.\n\n## Mitigation\nUsers should upgrade to **Zebra 4.3.0** or later immediately. \n\nIf an immediate upgrade is not possible, users should ensure their RPC port is not exposed to the Internet. However, the P2P port must remain closed or restricted to trusted peers to fully mitigate the risk, which may impact the node's ability to sync with the network.\n\n## Credits\nZebra thanks [robustfengbin](https://github.com/robustfengbin), who discovered this issue and reported it via coordinated disclosure process.\n\n---",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "zebrad"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.3.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "zebra-chain"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.0.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-qp6f-w4r3-h8wg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34202"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ZcashFoundation/zebra"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ZcashFoundation/zebra/releases/tag/v4.3.0"
  }, {
    "type" : "WEB",
    "url" : "https://zfnd.org/zebra-4-3-0-critical-security-fixes-zip-235-support-and-performance-improvements"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1336", "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-27T22:19:24Z",
    "nvd_published_at" : "2026-03-31T15:16:17Z"
  }
}