Skip to main content
VulnerabilityPublished

CVE-2026-123554: ZcashFoundation zebra · Inefficient Algorithmic Complexity

Affects ZcashFoundation zebraSource CVE Database V5

0
Compare

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

Data as of 8 Nov 2026, 02:06 UTC

CVSS 4.0 base score
8.7High
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.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 7.0.0
CVSS:4.0/AV:N/AC:L/AT:N/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
  • >=6.4.0 <7.0.0
Fixed in
  • 7.0.0
crates.iozebrapkg:cargo/zebraOther threatsAffected
  • >=6.4.0 <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 zebrad to version 7.0.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.

Description

Zebra zebrad versions 6.4.0 up to but not including 7.0.0 contain an inefficient algorithmic complexity issue in the mempool coinbase-maturity check. This inefficiency arises because the function Transaction::coinbase_spend_restriction() rebuilds the transaction's output list repeatedly for each spent outpoint, resulting in quadratic computational work. An attacker controlling a connected peer can exploit this by sending many unsigned transactions with numerous transparent inputs and outputs, which are rejected without penalty but cause verification threads to be pinned.

References

Community reviews

Loading reviews…