CVE-2026-44499: Zebrad Zebra Has Permanent Block Discovery Vulnerability

HIGH
Advisory Identifier: GHSA-h9hm-m2xj-4rq9
CWE-770
Published
Advisory Summary

CVE-2026-44499 is a HIGH zebra has permanent block discovery vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Zebrad libraries in the crates.io ecosystem. The issue involves zebra has permanent block discovery halt via gossip queue saturation and syncer poisoning. Remediation is available by upgrading affected packages to version 4.4.0.

CVE-2026-44499 at a Glance

CVE Identifier CVE-2026-44499
GHSA Identifier GHSA-h9hm-m2xj-4rq9
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Zebrad
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-44499

To remediate this vulnerability, upgrade all affected Zebrad dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

zebrad fixed: 4.4.0
Upgrade zebrad to 4.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for zebrad

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44499, inspect your project dependencies for Zebrad:

inspect dependencies for zebrad

Analyze the terminal output to locate any version of Zebrad in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Zebrad, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A composite denial-of-service vulnerability in Zebra's block discovery pipeline allows an unauthenticated remote attacker to permanently halt all new block discovery on a targeted node. The attack exploits three independent weaknesses in the gossip, syncer, and download subsystems — all exercisable from a single TCP connection — to create a monotonically growing block deficit that never self-heals. ## Severity **Critical** — This is a Denial of Service vulnerability that requires no authentication, no special privileges, and only a single peer connection. The halt is permanent: the node will never recover without operator intervention. ## Affected Versions All Zebra versions prior to 4.4.0. ## Description Zebra discovers new blocks through two complementary paths: a gossip path (peers announce blocks via `inv` messages, triggering individual block downloads) and a syncer path (Zebra periodically queries peers with `FindBlocks`/`FindHeaders` to discover chains of missing blocks). Both paths must function for normal operation. The gossip path was vulnerable because there was no per-connection rate limit on `inv` messages. A single connection could send enough sequential `inv` messages with fake block hashes to fill the entire gossip download queue in under a millisecond. The `FullQueue` return value was silently ignored, so legitimate block announcements from honest peers were dropped with no warning. The syncer backup path could be degraded by responding with empty `inv` to `FindBlocks` requests and with `NotFound` to block download requests. Both are valid protocol responses that carried zero misbehavior penalty. The attacker's connection was never banned and never disconnected, allowing the degradation to persist indefinitely. Combining these two vectors, an attacker could suppress both block discovery paths simultaneously from a single connection, causing the node to fall permanently behind the chain tip. ## Impact **Denial of Service** * **Attack Vector:** Network, unauthenticated. Requires only a single TCP peer connection. * **Effect:** Permanent halt of block discovery. The targeted node falls behind the chain tip and never recovers without operator intervention. * **Scope:** Any Zebra node reachable by the attacker over the peer-to-peer network. ## Fixed Versions This issue is fixed in Zebra 4.4.0. The fix drops connections that send empty responses to `FindBlocks` and `FindHeaders` messages, preventing attackers from degrading the syncer path without consequence. ## Mitigation Users should upgrade to Zebra 4.4.0 or later immediately. There are no known workarounds for this issue. Immediate upgrade is the only way to protect against this attack. ## Credits Zebra the researcher who reported this issue through the coordinated disclosure process.

CVE-2026-44499 Affected Zebrad Versions

1 component(s)
Fixed Versions:
4.4.0
Product / Package Ecosystem Affected Versions Fixed Version
zebrad
crates.io
< 4.4.0
4.4.0

References

Frequently Asked Questions

What is CVE-2026-44499?
CVE-2026-44499 is a security vulnerability in Zebrad involving Zebra has Permanent Block Discovery Halt via Gossip Queue Saturation and Syncer Poisoning under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Zebrad versions are affected?
Affected versions include releases prior to 4.4.0 across affected packages: zebrad.
What version fixes CVE-2026-44499?
Upgrading to 4.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is zebrad affected?
Yes, zebrad is affected in releases prior to 4.4.0. Upgrade your dependency to 4.4.0 or later.
What CWE is associated with CVE-2026-44499?
CVE-2026-44499 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check crates.io dependencies for CVE-2026-44499?
Run the dependency tree command: 'inspect dependencies for zebrad'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h9hm-m2xj-4rq9",
  "modified" : "2026-05-08T19:12:35Z",
  "published" : "2026-05-08T19:12:35Z",
  "aliases" : [ "CVE-2026-44499" ],
  "summary" : "Zebra has Permanent Block Discovery Halt via Gossip Queue Saturation and Syncer Poisoning",
  "details" : "## Summary\n\nA composite denial-of-service vulnerability in Zebra's block discovery pipeline allows an unauthenticated remote attacker to permanently halt all new block discovery on a targeted node. The attack exploits three independent weaknesses in the gossip, syncer, and download subsystems — all exercisable from a single TCP connection — to create a monotonically growing block deficit that never self-heals.\n\n## Severity\n\n**Critical** — This is a Denial of Service vulnerability that requires no authentication, no special privileges, and only a single peer connection. The halt is permanent: the node will never recover without operator intervention.\n\n## Affected Versions\n\nAll Zebra versions prior to 4.4.0.\n\n## Description\n\nZebra discovers new blocks through two complementary paths: a gossip path (peers announce blocks via `inv` messages, triggering individual block downloads) and a syncer path (Zebra periodically queries peers with `FindBlocks`/`FindHeaders` to discover chains of missing blocks). Both paths must function for normal operation.\n\nThe gossip path was vulnerable because there was no per-connection rate limit on `inv` messages. A single connection could send enough sequential `inv` messages with fake block hashes to fill the entire gossip download queue in under a millisecond. The `FullQueue` return value was silently ignored, so legitimate block announcements from honest peers were dropped with no warning.\n\nThe syncer backup path could be degraded by responding with empty `inv` to `FindBlocks` requests and with `NotFound` to block download requests. Both are valid protocol responses that carried zero misbehavior penalty. The attacker's connection was never banned and never disconnected, allowing the degradation to persist indefinitely.\n\nCombining these two vectors, an attacker could suppress both block discovery paths simultaneously from a single connection, causing the node to fall permanently behind the chain tip.\n\n## Impact\n\n**Denial of Service**\n\n* **Attack Vector:** Network, unauthenticated. Requires only a single TCP peer connection.\n* **Effect:** Permanent halt of block discovery. The targeted node falls behind the chain tip and never recovers without operator intervention.\n* **Scope:** Any Zebra node reachable by the attacker over the peer-to-peer network.\n\n## Fixed Versions\n\nThis issue is fixed in Zebra 4.4.0.\n\nThe fix drops connections that send empty responses to `FindBlocks` and `FindHeaders` messages, preventing attackers from degrading the syncer path without consequence.\n\n## Mitigation\n\nUsers should upgrade to Zebra 4.4.0 or later immediately.\n\nThere are no known workarounds for this issue. Immediate upgrade is the only way to protect against this attack.\n\n## Credits\n\nZebra the researcher who reported this issue through the coordinated disclosure process.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "zebrad"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-h9hm-m2xj-4rq9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44499"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ZcashFoundation/zebra"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T19:12:35Z",
    "nvd_published_at" : "2026-05-08T16:16:13Z"
  }
}