CVE-2026-104420: ZcashFoundation zebra · Incorrect Type Conversion or Cast
Affects ZcashFoundation zebraSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 6.3.0 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| ZcashFoundationzebra | Affected
| Fixed in
|
GitHubzcashfoundation/zebrapkg:github/zcashfoundation/zebraOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Zebra to version 6.3.0 or later, where this issue has been addressed. Patch status is confirmed by the affectedVersions field indicating versions before 6.3.0 are vulnerable. No vendor advisory content was provided, so check the official Zebra project resources for the official fix and further guidance.
Description
Zebra versions before 6.3.0 have a vulnerability in their misbehavior scoring mechanism. This flaw allows unauthenticated peers to bypass penalties by sending invalid gossiped blocks. The issue arises because the system incorrectly downcasts RouterError to VerifyBlockError during inbound cleanup, causing the misbehavior score to be discarded. As a result, attackers can repeatedly trigger block downloads and Equihash verification without being banned.