Zebra Network
Approved changes feed: RSS · Atom
cpe:2.3:a:zcashfoundation:zebra-network:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Zcashfoundation (d1eb1912-d66f-5e58-afb6-945663f2b85a) |
|---|---|
| Product | Zebra Network (e9815cc9-6f7f-5ca9-aa26-05c03b7a5723) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-40881 |
vulnerable | 2026-06-08 08:01:21.083136 |
Zebra: addr/addrv2 Deserialization Resource Exhaustion
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.0 and zebra-network version 5.0.1, when deserializing addr or addrv2 messages, which contain vectors of addresses, Zebra would fully deserialize them up to a maximum length (over 233,000) that was derived from the 2 MiB message size limit. This is much larger than the actual limit of 1,000 messages from the specification. Zebra would eventually check that limit but, at that point, the memory for the larger vector was already allocated. An attacker could cause out-of-memory aborts in Zebra by sending multiple such messages over different connections. This vulnerability is fixed in zebrad version 4.3.0 and zebra-network version 5.0.1.
Published: 2026-04-21T19:20:53.416Z
Updated: 2026-04-21T20:36:18.824Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.