https://feed.craftedsignal.io/tags/consensus-failure/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 07 May 2026 20:56:21 +0000https://feed.craftedsignal.io/briefs/2024-01-09-zebra-consensus-divergence/Thu, 07 May 2026 20:56:21 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-09-zebra-consensus-divergence/Zebra versions prior to 4.4.0 exhibit a consensus divergence vulnerability (CVE-2026-44497) due to insufficient error handling of invalid sighash types during sighash computation, potentially leading to network partitioning and double-spend attacks.Zebra, a Zcash node implementation, versions prior to 4.4.0 are vulnerable to a critical consensus divergence issue. This flaw, identified as CVE-2026-44497, stems from inadequate error handling when processing invalid sighash types during signature hash computation. Specifically, when an undefined hash type is encountered, Zebra’s foreign function interface (FFI) does not properly propagate the error from the Rust-based sighash computation callback to the C++ verification code. Consequently, the C++ checker may use a stale digest from a previous valid signature validation, leading to the acceptance of invalid transactions. This discrepancy can create a consensus split between Zebra and zcashd nodes, potentially disrupting the Zcash network. The vulnerability was introduced as a side effect of a previous fix (GHSA-8m29-fpq5-89jj).

Attack Chain

1. Attacker crafts a malicious transaction.
2. Transaction contains a transparent output.
3. The output is spent by a script that includes OP_CHECKSIGVERIFY and OP_CHECKSIG.
4. OP_CHECKSIGVERIFY is executed with a valid hash type, priming the C++ sighash buffer with a valid digest.
5. OP_CHECKSIG is executed with an undefined hash type.
6. Zebra’s Rust callback returns None due to the undefined hash type, but the C++ checker does not receive this signal.
7. The C++ checker verifies the invalid signature against the stale digest in the buffer.
8. Zebra incorrectly accepts the spend, while zcashd rejects it, leading to a consensus split.

Impact

The vulnerability can lead to a consensus failure within the Zcash network. An attacker can exploit this to cause network partitioning, where different nodes have conflicting views of the blockchain’s state. This can lead to service disruption for users relying on affected Zebra nodes. Furthermore, the vulnerability could potentially be exploited for double-spend attacks if a malicious miner relies on Zebra’s faulty validation results. While the impact is mitigated by the prevalence of zcashd among miners, any miner or template pipeline relying on Zebra’s validation is at risk.

Recommendation

• Upgrade all Zebra nodes to version 4.4.0 or later immediately to address CVE-2026-44497.
• Monitor Zebra node logs for unexpected consensus errors or forks following the upgrade.
• Evaluate the feasibility of implementing custom monitoring to detect divergence between Zebra and zcashd validation results within your environment.

]]>criticaladvisoryconsensus-failurevulnerabilitynetwork-partitionhttps://feed.craftedsignal.io/briefs/2026-05-zebra-sigops-undercount/Thu, 07 May 2026 20:54:33 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-zebra-sigops-undercount/Zebra's block validator undercounts signature operations, allowing it to accept invalid blocks, leading to a network split between Zebra and zcashd nodes.Zebra, a Zcash node implementation, contains a critical vulnerability where its block validator incorrectly calculates the number of signature operations (sigops) within a block. This flaw, present in versions prior to 4.4.0, stems from two distinct undercounting issues: incorrect handling of coinbase transactions and P2SH scripts. An attacker, typically a malicious miner, can exploit this to create blocks that Zebra accepts but zcashd rejects. This discrepancy leads to a consensus failure, causing a network split where Zebra nodes follow a different, invalid chain. This vulnerability poses a significant risk to network integrity for operators relying on Zebra for consensus.

Attack Chain

1. A malicious miner crafts a block with a high number of signature operations.
2. The miner hides sigops in the coinbase scriptSig (up to ~98 sigops).
3. The miner includes transactions with a high number of P2SH spends whose redeem scripts collectively exceed 20000 sigops.
4. Zebra’s block validator undercounts sigops due to the coinbase scriptSig and P2SH redeem script handling issues.
5. Zebra accepts the invalid block because the sigop count is below MAX_BLOCK_SIGOPS.
6. zcashd rejects the block due to accurately counting the excessive sigops.
7. Zebra nodes build on the invalid block, diverging from the main Zcash chain followed by zcashd nodes.
8. A network split occurs, where Zebra and zcashd nodes operate on separate chains.

Impact

The vulnerability results in a network split between Zebra and zcashd nodes. Zebra nodes may accept and propagate blocks that are considered invalid by the rest of the network, leading to transaction rollbacks and unpredictable behavior for users relying on Zebra for consensus. This could lead to a denial of service and financial losses for users of Zebra nodes. There is no information available regarding the number of victims or specific sectors targeted.

Recommendation

• Upgrade Zebra nodes to version 4.4.0 or later to patch the vulnerability as advised by the vendor.
• Monitor network consensus and validate Zebra’s chain against other Zcash implementations (zcashd) to detect potential forks caused by this vulnerability.
• Consider deploying network-level rules to identify blocks with unusually large coinbase scriptSig fields.
• Enable detailed logging for block validation processes in Zebra to investigate potential consensus failures.

]]>mediumadvisoryblockchainconsensus-failurezcash