Medium · CVSS 6.9CVE-2026-104432

Zebra before 6.3.0 False Readiness via Discarded One-Hash FindBlocks Response

Answer in brief

CVE-2026-104432 records a Medium severity (CVSS 6.9) vulnerability in Zebra before 6.3.0 False Readiness via Discarded One-Hash FindBlocks Response. The current sources do not mark it as known exploited. The current feed maps ZcashFoundation/zebra (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 2, 2026Updated Oct 2, 2026Source checked Oct 2, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ZcashFoundation/zebra (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ZcashFoundation/zebrageneric	>=0 <6.3.0	6.3.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for ZcashFoundation/zebra.
Review the reported fix. Update ZcashFoundation/zebra to 6.3.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 2, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.