Approved changes feed: RSS · Atom

cpe:2.3:a:zfnd:zebra-network:*:*:*:*:*:rust:*:*

part: a version: * update: *

VendorZfnd (86acb11b-50a5-5ca1-a20b-124d696a668f)
ProductZebra Network (1c2fd0be-9184-5b6f-8829-92dfceeb7371)
Edition*
Language*
Software edition*
Target softwarerust
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-44500 vulnerable 2026-06-08 08:05:11.116850 ZEBRA: Allocation Amplification in Inbound Network Deserializers
MEDIUM (5.3)
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.4.0, prior to zebra-chain version 7.0.0, and prior to zebra-network version 6.0.0, several inbound deserialization paths in Zebra allocated buffers sized against generic transport or block-size ceilings before the tighter protocol or consensus limits were enforced. An unauthenticated or post-handshake peer could therefore force the node to preallocate and parse for orders of magnitude more data than the protocol intended, across headers messages, equihash solutions in block headers, Sapling spend vectors in V5/V4 transactions, and coinbase script bytes in blocks. This issue has been patched in zebrad version 4.4.0, zebra-chain version 7.0.0, and zebra-network version 6.0.0.
Published: 2026-05-08T15:10:21.516Z
Updated: 2026-05-08T19:41:46.471Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-40881 vulnerable 2026-06-08 08:01:21.083918 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
Reference links
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.