Secuno
ENNL
Book demo

CVE-2026-41583

Zfnd Zebrad vulnerability

9.1 CRITICALEPSS 0.47%
  1. Published8 May 2026

Description

ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade. Zebra nodes could thus accept and eventually mine a block that would be considered invalid by zcashd nodes, creating a consensus split between Zebra and zcashd nodes. In a similar vein, for V4 transactions, Zebra mistakenly used the "canonical" hash type when computing the sighash while zcashd (correctly per the spec) uses the raw value, which could also crate a consensus split. This issue has been patched in zebrad version 4.3.1 and zebra-script version 5.0.2.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected products

Zfnd Zebrad< 4.3.1
Zfnd Zebra-script< 5.0.2

Remediation

Fixed in
Zfnd Zebrad≥ 4.3.1
Zfnd Zebra-script≥ 5.0.2

References

Frequently asked

Is CVE-2026-41583 being actively exploited?

CVE-2026-41583 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.47%.

How severe is CVE-2026-41583?

CVE-2026-41583 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.47% probability of exploitation.

Which products are affected by CVE-2026-41583?

Affected products include Zfnd Zebrad, Zfnd Zebra-script.

How do I fix CVE-2026-41583?

Upgrade affected software to a fixed version, for example Zfnd Zebrad 4.3.1, Zfnd Zebra-script 5.0.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-41583 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.