Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect as P2P peer to target Zebra node
-
DeliveryCraft coinbase-malleated block colliding on canonical hash
-
ExploitDeliver before canonical block propagates
-
ExecutionPoison parent_error_map in state write task
-
ImpactNext canonical block rejected, sync stalls ~2000 blocks
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incomplete cleanup
|
| Exploitation Conditions | Exploitation requires the attacker to act as a network peer and deliver a coinbase-malleated block that shares a legitimate canonical block's hash to the target Zebra node BEFORE the canonical block propagates - a race-condition timing window reflected in AC:H and AT:P. No authentication is required (PR:N, unauthenticated peers), and no user interaction is needed (UI:N), but the narrow pre-propagation timing window and the need to produce a hash-colliding malleated block materially limit reliable, on-demand exploitation. Impact is confined to availability: the node stalls synchronization for roughly 2,000 blocks; there is no confidentiality or integrity impact. Affects all Zebra versions before 6.1.0; upgrading to 6.1.0 remediates. |
| Impact | The CVSS 4.0 vector (CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N) describes a network-reachable, unauthenticated flaw whose only impact is availability (VA:H; VC:N/VI:N/VA:H), i.e. a denial-of-service chain-stall rather than any data exposure or integrity loss. Two metrics meaningfully dampen the 8.2 score in practice: AC:H and AT:P indicate the attacker must win a timing race, delivering a coinbase-malleated block that shares a canonical block's hash BEFORE that canonical block propagates - a non-trivial, non-repeatable-on-demand condition. There is no EPSS score, no CISA KEV listing, and no POC referenced in the provided data, so this is no public exploit identified at time of analysis; the risk is theoretical-but-credible, not actively exploited. CONFLICT TO NOTE: the input Tags include 'Information Disclosure', which directly contradicts the CVSS vector (VC:N, confidentiality impact is None) and the description (a synchronization stall) - this is a mislabeling, not an information-disclosure bug. Net: a genuine availability/integrity-of-sync concern for Zebra operators worth patching to 6.1.0, but the attack-complexity and timing prerequisites make opportunistic mass exploitation unlikely; prioritize based on node criticality rather than treating it as an internet-wide emergency. |
| Exploit ScenarioDerived | A malicious peer on the Zcash P2P network crafts a block that is coinbase-malleated yet collides on the canonical block's hash, and races to deliver it to a target Zebra node before the legitimate canonical block propagates. The poisoned parent_error_map entry then causes the node to reject the next canonical block, stalling synchronization for roughly 2,000 blocks. No public exploit code is referenced, and the required pre-propagation timing window (AC:H/AT:P) makes reliable exploitation difficult. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Denial of service in the Zcash Foundation's Zebra full node before 6.1.0 lets remote unauthenticated peers stall node synchronization by poisoning the stale parent_error_map used by the state write task, after which the next canonical block is rejected for roughly 2,000 blocks. Exploitation is gated by a narrow race window: the attacker must act as a network peer and deliver a coinbase-malleated block that shares a legitimate canonical block's hash before that canonical block propagates, an AC:H/AT:P timing condition, so reliable on-demand abuse is materially limited. Impact is availability-only (CVSS 4.0 8.2, VA:H with no confidentiality or integrity effect), unauthenticated per the PR:N vectors, and no public exploit code has been identified at time of analysis; a vendor-released patch is available in Zebra 6.1.0.
RemediationAI
Vendor-released patch: upgrade Zebra to 6.1.0, which contains the cleanup fix for the state write task; the fix is documented in the GitHub security advisory GHSA-8gxx-hc65-vv82, with supporting detail in VulnCheck's advisory at https://www.vulncheck.com/advisories/zebra-before-6.1.0-chain-stall-via-stale-parent-error-map-entry. Update promptly on any internet-facing or peer-exposed node, and verify the running binary reports 6.1.0 or later after restart, since the poisoned parent_error_map entries live in memory and a restart alone will clear a stalled state without preventing re-triggering. If upgrading cannot be done immediately, reduce exposure by restricting peer connectivity to a trusted allowlist-for example using Zebra's peer-connection configuration to dial only known-good peers and refusing inbound connections-accepting the trade-off that this narrows peer diversity, can slow block discovery, and weakens the node's contribution to the network; a node with no inbound listening port is harder to reach but still attackable by a malicious node it chooses to connect to. Operators should also monitor logs for repeated canonical-block rejections or a prolonged sync stall and treat them as a signal of exploitation, and can restart the node to recover availability, but these are containment measures rather than fixes and do not address the incomplete cleanup that enables the attack.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Zebra is the Rust implementation of a Zcash consensus full node, and the flaw sits in the state write task that tracks block-validation bookkeeping. Root cause is CWE-459 (incomplete cleanup): entries written into the parent_error_map keyed by block hash are not purged when the corresponding block ceases to be relevant, leaving a persistent stale record. Because the map is hash-keyed, an attacker-supplied coinbase-malleated block that collides with the hash of a legitimate canonical block can seed an erroneous entry that is later applied to the canonical block arriving after it, causing that block-and therefore chain extension-to be rejected. The result is a synchronization stall of approximately 2,000 blocks rather than a consensus split or data compromise. Exposure tracks CPE cpe:2.3:a:zcashfoundation:zebra:*:*:*:*:*:*:*:* and covers all pre-6.1.0 builds; the vulnerability is reachable from the peer-to-peer network layer, meaning any node that accepts connections from untrusted peers is in scope, while the attacker needs only coinbase malleability and the pre-propagation timing advantage rather than credentials or user action.
Know when Zebra gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Unauthenticated network peer (AV:N/PR:N) but a pre-propagation timing race drives AC:H; impact is a sync stall only, so C:N/I:N/A:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Zebra before 6.1.0 contains an incomplete cleanup vulnerability in the state write task that allows remote unauthenticated peers to stall node synchronization by poisoning parent_error_map. Attackers can deliver a coinbase-malleated block sharing a canonical block's hash before it propagates, causing the next canonical block to be rejected and stalling the node for roughly 2,000 blocks.
Technical POC Analysis
Note on identifiers: the supplied evidence is GHSA-8gxx-hc65-vv82, which rates this Moderate (CVSS 3.1 5.9, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) and records "No known CVE".
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A high-severity availability flaw in the Zcash Foundation's Zebra full node software (versions prior to 6.1.0) allows any unauthenticated network peer to stall node synchronization, causing the node to reject the next valid block for an extended period of roughly 2,000 blocks. Organizations operating Zebra nodes for Zcash transaction validation, exchange deposits/withdrawals, custody, or mining infrastructure could experience prolonged synchronization outages that delay settlement and block-processing operations. The attack requires a narrow timing race, so opportunistic abuse is limited, but the vendor has released a fix and the exposure is fully avoidable through timely upgrade.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Remote denial-of-service in Zebra (Zcash node implementation) versions prior to 4.4.0 allows unauthenticated attackers t
Motorola FX9500 devices allow remote attackers to conduct absolute path traversal attacks, as demonstrated by PL/SQL Ser
An issue was discovered on Zebra (formerly Motorola Solutions) Fixed RFID Reader FX9500 devices. Rated critical severity
Remote, unauthenticated denial of service in Zcash Foundation's Zebra full node: versions 6.4.0 through 6.4.1 abort when
Unauthenticated denial of service in Zebra (Zcash Foundation's full node implementation) before 6.0.0 allows remote peer
Remote unauthenticated attackers can cause a consensus divergence in Zcash Zebra nodes (zebrad 4.5.0 and zebra-script 7.
Zcash Foundation's Zebra full node (zebrad) before 6.2.1 can be stalled in block verification by any unauthenticated pee
Block-sync denial of service in Zebra (zebrad), the Rust implementation of a Zcash full node, affects all versions befor
Consensus divergence in Zebra Zcash nodes before 4.4.0 allows unauthenticated remote attackers to craft V5 transparent t
Zcash Zebra nodes running zebrad 4.4.0 or zebra-script 6.0.0 incorrectly accept V5 transparent transactions in which a S
Denial of service in the Zcash Foundation's Zebra full node implementation before 6.1.0 allows an unauthenticated remote
Zebra Industrial Printers All Versions, Zebra printers are shipped with unrestricted end-user access to front panel opti
EUVD-2026-91438
GHSA-3c42-fjf2-4p66
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB