CVE-2026-34377: Zebra consensus Zebra Has A Consensus Failure Vulnerability

HIGH
Advisory Identifier: GHSA-3vmh-33xr-9cqh
CWE-347
Published
Advisory Summary

CVE-2026-34377 is a HIGH zebra has a consensus failure vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Zebra consensus libraries in the crates.io ecosystem. The issue involves zebra has a consensus failure due to improper verification of v5 transactions. Remediation is available by upgrading affected packages to version 5.0.1, 4.3.0.

CVE-2026-34377 at a Glance

CVE Identifier CVE-2026-34377
GHSA Identifier GHSA-3vmh-33xr-9cqh
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Zebra consensus
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-34377

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

zebra-consensus fixed: 5.0.1
Upgrade zebra-consensus to 5.0.1
zebrad fixed: 4.3.0
Upgrade zebrad to 4.3.0
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 zebra-consensus

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34377, inspect your project dependencies for Zebra consensus:

inspect dependencies for zebra-consensus

Analyze the terminal output to locate any version of Zebra consensus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.1), 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-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Zebra consensus, 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

--- # CVE-2026-34377: Consensus Failure via Crafted V5 Authorization Data ## Summary A logic error in Zebra's transaction verification cache could allow a malicious miner to induce a consensus split. By matching a valid transaction's `txid` while providing invalid authorization data, a miner could cause vulnerable Zebra nodes to accept an invalid block, leading to a consensus split from the rest of the Zcash network. To be clear, **this would not allow invalid transactions to be accepted** but could result in a consensus split between vulnerable Zebra nodes and invulnerable Zebra and Zcashd nodes. ## Severity **High** - This is a Consensus Vulnerability that could allow a malicious miner to induce network partitioning, service disruption, and potential double-spend attacks against affected nodes. ## Affected Versions All Zebra versions supporting V5 transactions (Network Upgrade 5 and later) prior to **version 4.3.0**. ## Description The vulnerability exists in the `find_verified_unmined_tx` function within `transaction.rs`. This function was designed to optimize block verification by checking if a transaction was already verified in the mempool. The lookup mechanism used the **ZIP-244 `txid`** as the unique key. However, for V5 transactions, the `txid` specifically excludes the **Authorization Data Root** (signatures and proofs). Because Zebra returned a "verified" status based solely on the `txid`, it skipped the essential `check_v5_auth()` call for the transaction version provided in the block. An attacker (specifically a malicious miner) could exploit this by: 1. Observing a valid V5 transaction broadcast to the network and entering a Zebra node's mempool. 2. Creating a block containing a modified version of that transaction. The modified version has the same `txid` but contains invalid signatures or proofs. 3. The affected Zebra node identifies the `txid` in its mempool and incorrectly assumes the block's version of the transaction is already verified. 4. The node commits the block with the invalid transaction data. 5. Other nodes (like `zcashd` or `zebra` nodes without that transaction in their mempool) reject the block, resulting in a chain fork where the poisoned Zebra node is isolated. ## Impact **Consensus Failure** * **Attack Vector:** Network (specifically via a malicious miner). * **Effect:** Network partition/consensus split. * **Scope:** Any Zebra node utilizing the transaction verification cache optimization for V5 transactions. ## Fixed Versions This issue is fixed in **Zebra 4.3.0**. The fix ensures that verification is only skipped if the transaction's full integrity—including authorization data—is validated against the mempool entry. ## Mitigation Users should upgrade to **Zebra 4.3.0** or later immediately. There are no known workarounds for this issue. Immediate upgrade is the only way to ensure the node remains on the correct consensus path and is protected against malicious chain forks. ## Resources * [Zebra 4.3.0 Release Announcement](https://zfnd.org/zebra-4-3-0-critical-security-fixes-zip-235-support-and-performance-improvements/) * [ZIP-244: Transaction Identifier](https://zips.z.cash/zip-0244) ---

CVE-2026-34377 Affected Zebra consensus Versions

2 component(s)
Fixed Versions:
5.0.14.3.0
Product / Package Ecosystem Affected Versions Fixed Version
zebra-consensus
crates.io
< 5.0.1
5.0.1
zebrad
crates.io
< 4.3.0
4.3.0

References

Frequently Asked Questions

What is CVE-2026-34377?
CVE-2026-34377 is a security vulnerability in Zebra consensus involving Zebra has a Consensus Failure due to Improper Verification of V5 Transactions under CWE-347: Improper Verification of Cryptographic Signature.
Which Zebra consensus versions are affected?
Affected versions include releases prior to 5.0.1, 4.3.0 across affected packages: zebra-consensus, zebrad.
What version fixes CVE-2026-34377?
Upgrading to 5.0.1, 4.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is zebra-consensus affected?
Yes, zebra-consensus is affected in releases prior to 5.0.1. Upgrade your dependency to 5.0.1 or later.
Is zebrad affected?
Yes, zebrad is affected in releases prior to 4.3.0. Upgrade your dependency to 4.3.0 or later.
What CWE is associated with CVE-2026-34377?
CVE-2026-34377 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check crates.io dependencies for CVE-2026-34377?
Run the dependency tree command: 'inspect dependencies for zebra-consensus'. 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-3vmh-33xr-9cqh",
  "modified" : "2026-03-31T18:52:14Z",
  "published" : "2026-03-30T19:13:41Z",
  "aliases" : [ "CVE-2026-34377" ],
  "summary" : "Zebra has a Consensus Failure due to Improper Verification of V5 Transactions",
  "details" : "---\n\n# CVE-2026-34377: Consensus Failure via Crafted V5 Authorization Data\n\n## Summary\nA logic error in Zebra's transaction verification cache could allow a malicious miner to induce a consensus split. By matching a valid transaction's `txid` while providing invalid authorization data, a miner could cause vulnerable Zebra nodes to accept an invalid block, leading to a consensus split from the rest of the Zcash network.  To be clear, **this would not allow invalid transactions to be accepted** but could result in a consensus split between vulnerable Zebra nodes and invulnerable Zebra and Zcashd nodes.\n\n## Severity\n**High** - This is a Consensus Vulnerability that could allow a malicious miner to induce network partitioning, service disruption, and potential double-spend attacks against affected nodes.\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 exists in the `find_verified_unmined_tx` function within `transaction.rs`. This function was designed to optimize block verification by checking if a transaction was already verified in the mempool.\n\nThe lookup mechanism used the **ZIP-244 `txid`** as the unique key. However, for V5 transactions, the `txid` specifically excludes the **Authorization Data Root** (signatures and proofs). Because Zebra returned a \"verified\" status based solely on the `txid`, it skipped the essential `check_v5_auth()` call for the transaction version provided in the block.\n\nAn attacker (specifically a malicious miner) could exploit this by:\n1. Observing a valid V5 transaction broadcast to the network and entering a Zebra node's mempool.\n2. Creating a block containing a modified version of that transaction. The modified version has the same `txid` but contains invalid signatures or proofs.\n3. The affected Zebra node identifies the `txid` in its mempool and incorrectly assumes the block's version of the transaction is already verified.\n4. The node commits the block with the invalid transaction data.\n5. Other nodes (like `zcashd` or `zebra` nodes without that transaction in their mempool) reject the block, resulting in a chain fork where the poisoned Zebra node is isolated.\n\n## Impact\n**Consensus Failure**\n* **Attack Vector:** Network (specifically via a malicious miner).\n* **Effect:** Network partition/consensus split.\n* **Scope:** Any Zebra node utilizing the transaction verification cache optimization for V5 transactions.\n\n## Fixed Versions\nThis issue is fixed in **Zebra 4.3.0**. \n\nThe fix ensures that verification is only skipped if the transaction's full integrity—including authorization data—is validated against the mempool entry.\n\n## Mitigation\nUsers should upgrade to **Zebra 4.3.0** or later immediately. \n\nThere are no known workarounds for this issue. Immediate upgrade is the only way to ensure the node remains on the correct consensus path and is protected against malicious chain forks.\n\n## Resources\n* [Zebra 4.3.0 Release Announcement](https://zfnd.org/zebra-4-3-0-critical-security-fixes-zip-235-support-and-performance-improvements/)\n* [ZIP-244: Transaction Identifier](https://zips.z.cash/zip-0244)\n\n---",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/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-consensus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.0.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-3vmh-33xr-9cqh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34377"
  }, {
    "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"
  }, {
    "type" : "WEB",
    "url" : "https://zips.z.cash/zip-0244"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-30T19:13:41Z",
    "nvd_published_at" : "2026-03-31T15:16:19Z"
  }
}