Skip to main content

CVE-2026-104432: Improper Check for Unusual or Exceptional Conditions in ZcashFoundation zebra

0
Medium
Published: 10/02/2026 (10/02/2026, 12:31:15 UTC)
Source: CVE Database V5
Vendor/Project: ZcashFoundation
Product: zebra

Description

Zebra before 6.3.0 contains an improper exceptional condition check in ChainSync::obtain_tips that discards valid one-hash FindBlocks responses, falsely reporting close-to-tip status. Peers returning only the next block hash cause a zero-length sync sample, making the /ready endpoint return 200 OK while the node remains behind the tip.

CVSS v4.0

Score 6.9medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
None
Vuln. Availability
Low
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Affected software

ZcashFoundation

zebra

Affected versions
>=0 <6.3.0
GitHub Actionsmore threats →ai
zcashfoundation/zebra
pkg:github/zcashfoundation/zebra
Affected versions
>=0 <6.3.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/02/2026, 12:02:11 UTC

Technical Analysis

CVE-2026-104432 affects Zebra prior to version 6.3.0. The vulnerability is an improper exceptional condition check in the ChainSync::obtain_tips function. This causes valid one-hash FindBlocks responses to be discarded, leading to false reporting of close-to-tip status. Specifically, when peers return only the next block hash, the sync sample length is zero, causing the /ready endpoint to incorrectly indicate the node is synchronized (HTTP 200 OK) while it is actually behind the blockchain tip.

Potential Impact

The vulnerability causes Zebra nodes to falsely report synchronization status, potentially misleading monitoring systems or operators into believing the node is up to date when it is not. This could affect the reliability of node status reporting but does not directly indicate a compromise or data loss. There are no known exploits in the wild.

Mitigation Recommendations

A fix is available in Zebra version 6.3.0. Users should upgrade to version 6.3.0 or later to remediate this issue. No other mitigation steps are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-02T00:50:26.603Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6abf99b0a43b0b3b89b26946

Added to database: 10/02/2026, 11:46:56 UTC

Last enriched: 10/02/2026, 12:02:11 UTC

Last updated: 10/03/2026, 03:07:31 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses