---

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, who discovered this issue and reported it via coordinated disclosure process.

---

CVE-2026-44500: Allocation Amplification in Inbound Network Deserializers

Summary

Several inbound deserialization paths in Zebra allocated buffers sized against generic transport or block-size ceilings before the tighter protocol or consensus limits were enforced. An unauthenticated or post-handshake peer could therefore force the node to preallocate and parse for orders of magnitude more data than the protocol intended, across headers messages, equihash solutions in block headers, Sapling spend vectors in V5/V4 transactions, and coinbase script bytes in blocks.

Severity

Moderate - This is a Denial-of-Service Vulnerability that could allow a malicious peer to amplify per-message memory and parse cost on Zebra nodes, with effects amplified by multi-peer fan-in.

Each individual case is bounded by the 2 MiB transport ceiling or the block-size cap, so no single message causes unbounded allocation, but the cumulative gap between intended and actual limits is significant.

Affected Versions

All Zebra versions prior to 4.4.0.

Description

Zebra's network codec uses TrustedPreallocate and generic Vec deserialization to bound inbound message parsing. In several places the bound used at the deserializer was the generic transport or block-size ceiling rather than the tighter protocol or consensus rule that applies to the field, so allocation happened first and the real limit was only enforced afterwards. Four such cases were identified:

- headers message receive cap. readheaders() deserialized the CountedHeader vector via the generic TrustedPreallocate path, which allowed up to ~1,409 entries per message. The protocol ceiling MAXFINDBLOCKHEADERSRESULTS = 160 was only used on the send side, giving an ~8.8x preallocation gap on receive. Reachable before the version handshake completes since the codec is installed on raw bytes. - Equihash solution length. Solution::zcashdeserialize decoded the solution as a generic Vec<u8> and only checked the exact consensus size (1344 bytes mainnet/testnet, 36 bytes regtest) afterwards in Solution::frombytes. A single fixed-size header field could be inflated to nearly the full block-size ceiling before rejection. - Sapling spend vectors in coinbase transactions. V5 spendprefixes and V4 shieldedspends were allocated generically with block-size-derived ceilings (~5,681 / ~5,208 entries) before the consensus rule that coinbase transactions have zero Sapling spends was enforced in the verifier. - Coinbase script bytes. Input::zcashdeserialize() read the coinbase script as a generic Vec<u8> up to the message-size cap before enforcing the consensus rule that coinbase scripts are between 2 and 100 bytes.

An attacker could exploit this by:

- Opening an inbound TCP connection (and, for the latter three cases, completing the version handshake). - Sending one of: a headers message with a CompactSize count up to ~1,409, a block whose header carries an inflated equihash CompactSize, a tx declaring a coinbase input with a large nSpendsSapling, or a block with a coinbase input whose script length is near the message-size ceiling. - The deserializer allocates against the loose ceiling, parses, and only then rejects.

Impact

Denial of Service

- Attack Vector: Network. - Effect: Amplified per-message allocation and parse cost on inbound peer messages, stackable across concurrent connections. The concrete effect will be influenced by how much memory Zebra has available. - Scope: Any affected Zebra node.

Fixed Versions

This issue is fixed in Zebra 4.4.0.

Mitigation

Users should upgrade to Zebra 4.4.0 or later immediately.

There are no known workarounds for this issue. Immediate upgrade is the only way to remove the amplified allocation surface on inbound peer messages.

Credits

Zebra thanks @Zk-nd3r for finding and reporting the issues.

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.