CVE-2026-104435: Zebra 4.4.0 Consensus Divergence via V5 SIGHASH_SINGLE Without Output

Published Oct 2, 2026
·
Updated

Zebra zebrad 4.4.0 and zebra-script 6.0.0 fail to enforce a ZIP-244 consensus rule, accepting V5 transparent inputs signed with SIGHASHSINGLE that lack a corresponding output. Attackers can broadcast crafted V5 transactions with more inputs than outputs that Zebra accepts but zcashd rejects, causing a network consensus split.

Affected Software

2 affected components
Zebra zebrad=4.4.0
Zebra zebra-script=6.0.0

Event History

Oct 2, 2026
CVE Published
via MITRE·11:38 AM
Data Sourced
via MITRE·11:38 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Zebra components are affected?

The affected components are zebrad 4.4.0 and zebra-script 6.0.0.

2

What must an attacker send to trigger the inconsistency?

An attacker must broadcast a crafted V5 transaction with more transparent inputs than outputs, where an input uses SIGHASH_SINGLE without a corresponding output. The transaction is accepted by Zebra but rejected by zcashd.

3

How can an operator determine whether they are exposed?

Operators using zebrad 4.4.0 or zebra-script 6.0.0 are affected by the described consensus-rule enforcement failure. The issue concerns validation of V5 transparent-input transactions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203