CVE-2026-104432: ZcashFoundation zebra · Unchecked Error Condition
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
A fix is available in Zebra version 6.3.0. Users should upgrade to version 6.3.0 or later to resolve this issue. No other mitigation steps are indicated or necessary according to the available data.
Description
Zebra versions before 6.3.0 have an improper check for exceptional conditions in the ChainSync::obtain_tips function. This flaw causes the node to discard valid one-hash FindBlocks responses, incorrectly reporting that it is close to the blockchain tip. As a result, peers that return only the next block hash cause a zero-length sync sample, making the /ready endpoint return a 200 OK status even though the node is behind the tip.