Status: UPDATED | Advisory ID: CVE-2026-40881
| CVE | CVE-2026-40881 |
| CVSS Score / Version | 7.5 (High) / CVSS v3.1 |
| Updated | 2026-06-17 |
| CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CVSS Prose | attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is none; availability impact is high. |
| Affected products | zfnd zebra-network and zfnd zebrad |
| Classified as | CWE-770 (Allocation of Resources Without Limits or Throttling) |
| Vendor | Product | Affected Versions | Patch Status |
|---|---|---|---|
| zfnd | zebra-network | ||
| zfnd | zebrad |
| Subsystems | General OT |
| Sectors | Multiple |
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. (NVD)
Monitor zfnd's web page for any future patch releases. See vendor advisory link below.