Skip to main content
VulnerabilityPublished

CVE-2026-123557: ZcashFoundation zebra · Reachable Assertion

Affects ZcashFoundation zebraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 7.0.0 soon.

Data as of 8 Nov 2026, 02:06 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 7.0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 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 7 Nov 2026.

What to do

Upgrade ZcashFoundation zebra to 7.0.0.

Affected software

ProductAffectedFixed in
ZcashFoundationzebraAffected
  • <7.0.0
Fixed in
  • 7.0.0
crates.iozebrapkg:cargo/zebraOther threatsAffected
  • <7.0.0
Fixed in
  • 7.0.0

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 7.0.0 or later, where this vulnerability is fixed. No other mitigations are indicated or required by the vendor advisory.

Description

ZcashFoundation Zebra versions before 7.0.0 contain a reachable assertion race condition that can be triggered by unauthenticated remote peers. This flaw allows malicious peers to abort the node by causing disconnection during a blocked outbound send. Attackers can exploit this by sending empty FindBlocks or FindHeaders replies and ceasing to read their socket, which leads to unresolved client response handling and termination of syncing nodes. The issue is fixed in version 7.0.0.

References

Community reviews

Loading reviews…