Skip to main content
VulnerabilityPublished

CVE-2026-104422: ZcashFoundation zebra · Insufficient Verification of Data Authenticity

Affects ZcashFoundation zebraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 6.3.0 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.3.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade zebra and zcashfoundation/zebra to 6.3.0.

Affected software

ProductAffectedFixed in
ZcashFoundationzebraAffected
  • <6.3.0
Fixed in
  • 6.3.0
GitHubzcashfoundation/zebrapkg:github/zcashfoundation/zebraOther threatsAffected
  • <6.3.0
Fixed in
  • 6.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Zebra version 6.3.0 and later. Users should upgrade to version 6.3.0 or newer to resolve this vulnerability. No additional mitigation steps are indicated in the provided data.

Description

The block sync download path in Zebra (zebrad) before 6.3.0 reads a block's height from its unvalidated coinbase scriptSig and drops blocks that appear too far behind the tip before consensus validation, without penalizing the supplying peer. Because V5 transaction IDs exclude the scriptSig, a malicious peer can repeatedly serve a canonical block whose coinbase claims height 1 while keeping the requested hash, delaying the node's discovery of the newest block.

References

Community reviews

Loading reviews…