dbcve.org
Zebra ScriptApplication · Zfnd

CVE-2026-44497

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 4.4.0 / 6.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.4.0 and prior to zebra-script version 6.0.0, the fix for CVE-2026-41583 introduced a separate issue due to insufficient error handling of the case where the sighash type is invalid, during sighash computation. Instead of returning an error, the normal flow would resume, and the input sighash buffer would be left untouched. In scenarios where a previous signature validation could leave a valid sighash in the buffer, an invalid hash-type could be incorrectly accepted, which would create a consensus split between Zebra and zcashd nodes. This issue has been patched in zebrad version 4.4.0 and zebra-script version 6.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In ZEBRA's sighash computation, when an invalid sighash type is encountered, insufficient error handling allows execution to continue without returning an error, leaving the input sighash buffer untouched. If a previous signature validation left a valid sighash in the buffer, this can allow invalid hash-types to be incorrectly accepted, causing a consensus split between Zebra and zcashd nodes.

MitigationUpgrade zebrad to version 4.4.0 or later and zebra-script to version 6.0.0 or later to incorporate the patched error handling for sighash type validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zebra ScriptApplication
Affected:< 6.0.0
ZebradApplication
Affected:< 4.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check zebrad version
    Run 'zebrad --version' or 'zebrad -V' from the command line to obtain the installed zebrad binary version
    Affected if The version shown is less than 4.4.0
  2. Check zebra-script version
    Run 'zebra-script --version' or check the installed package version through your system's package manager (dpkg, rpm, cargo, or similar)
    Affected if The version shown is less than 6.0.0
  3. Identify affected components in environment
    List all Zebra-related binaries and scripts installed in the system (such as zebrad, zebra-script, or any zebra-* packages) using 'which zebrad' or your system's package listing tools
    Affected if Any installed zebra component is found with a version below the safe thresholds (zebrad < 4.4.0 or zebra-script < 6.0.0)

You are affected if any installed zebrad version is below 4.4.0 or any installed zebra-script version is below 6.0.0, as these versions contain the flawed sighash validation that can cause consensus splits with zcashd.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.0 / 6.0.0 or later
Fixed in 4.4.06.0.0
Interim mitigation

Upgrade zebrad to version 4.4.0 or later and zebra-script to version 6.0.0 or later to incorporate the patched error handling for sighash type validation.

Recommended fix High confidence

zebrad version 4.4.0 or higher; zebra-script version 6.0.0 or higher

  1. Identify current zebrad version using 'zebrad --version'
  2. Identify current zebra-script version from Cargo.lock or dependency configuration
  3. For zebrad: Update to version 4.4.0 or later in Cargo.toml with 'zebrad = {"version" = ">=4.4.0"}'
  4. For zebra-script: Update to version 6.0.0 or later in Cargo.toml with 'zebra-script = {"version" = ">=6.0.0"}'
  5. Run 'cargo build' or 'cargo update' to fetch and compile the fixed versions
  6. Rebuild the zebra project with updated dependencies
  7. Restart zebrad service to apply the patched version
  8. Verify installation by running 'zebrad --version' to confirm version 4.4.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zebra Script Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44497 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data