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.
CVE-2026-44500
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 28.3%
- KEV
- Not listed
Published
May 8, 2026
Last Modified
May 8, 2026
Advisory Details (1)
Auto-updated Jun 16, 2026Allocation Amplification in Inbound Network Deserializers · Advisory · ZcashFoundation/zebra · GitHub
https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-438q-jx8f-cccvAffected Packages
(3 across 1 ecosystem)
crates.io(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| zebra-chain | — | 7.0.0 | — |
| zebrad | — | 4.4.0 | — |
| zebra-network | — | 6.0.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 37× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:09 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 21:20 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
Show 58 moreShow fewer
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 08:06 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 02:38 UTCEG score recompute
- 2026-06-14 02:31 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 09:26 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 09:15 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 09:04 UTCEG score recompute
- 2026-06-09 08:57 UTCEG score recompute
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 08:44 UTCEG score recompute
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 08:37 UTCEG score recompute
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 08:30 UTCEG score recompute
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 08:23 UTCEG score recompute
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 08:14 UTCEG score recompute
- 2026-06-03 07:56 UTCEG score recompute
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 07:49 UTCEG score recompute
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 07:40 UTCEG score recompute
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-26 13:44 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-23 00:07 UTCEG score recompute
- 2026-05-21 22:43 UTCEPSS rescore
- 2026-05-20 22:38 UTCEPSS rescore
- 2026-05-20 13:33 UTCEG score recompute
- 2026-05-20 11:22 UTCEPSS rescore
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-44500?
When was CVE-2026-44500 disclosed?
Is CVE-2026-44500 actively exploited?
What is the CVSS score of CVE-2026-44500?
How do I remediate CVE-2026-44500?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44500
Is Your Infrastructure Affected by CVE-2026-44500?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.