CVE Tools
Track your stack

CVE-2026-44500

ZEBRA: Allocation Amplification in Inbound Network Deserializers

No known exploitation. EPSS puts it in the 34th percentile. Fixed versions are out.

CVSS 3.15.3MediumEPSS percentile34th0.4% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix4 products3 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • ZcashFoundation zebraAffected: zebrad < 4.4.0Upgrade to: not statedAffected: zebra-chain < 7.0.0Upgrade to: not statedAffected: zebra-network < 6.0.0Upgrade to: not statedStated by: CVE record
  • Zfnd Zebra-chainAffected: < 7.0.0Upgrade to: 7.0.0Stated by: NVD
  • Zfnd Zebra-networkAffected: < 6.0.0Upgrade to: 6.0.0Stated by: NVD
  • Zfnd ZebradAffected: < 4.4.0Upgrade to: 4.4.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS34th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 34th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 0 days, from the signal feeds we watch.

  1. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Scored 5.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Zebra-chain, not every advisory.