CVE-2026-52732: Zebrad Zebrad Has Mempool Transaction Admission Vulnerability
MODERATECVE-2026-52732 is a MODERATE (CVSS 5.3) zebrad has mempool transaction admission vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Zebrad libraries in the crates.io ecosystem. The issue involves zebrad has mempool transaction admission denial via single-peer inbound queue saturation. Remediation is available by upgrading affected packages to version 4.5.0.
CVE-2026-52732 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
How to Fix CVE-2026-52732
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.
Upgrade zebrad to 4.5.0
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-52732, 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.5.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
CVE-2026-52732 Affected Zebrad Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
zebrad
|
crates.io |
< 4.5.0
|
4.5.0
|
References
Frequently Asked Questions
What is CVE-2026-52732?
Which Zebrad versions are affected?
What version fixes CVE-2026-52732?
Is zebrad affected?
What is the CVSS score of CVE-2026-52732?
What CWE is associated with CVE-2026-52732?
How can I check crates.io dependencies for CVE-2026-52732?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4fc2-h7jh-287c",
"modified" : "2026-07-02T19:39:02Z",
"published" : "2026-07-02T19:39:02Z",
"aliases" : [ "CVE-2026-52732" ],
"summary" : "zebrad has mempool transaction admission denial via single-peer inbound queue saturation",
"details" : "### Am I affected\n\nYou are affected if:\n\n1. You run `zebrad` up to and including `v4.4.1`.\n2. Your node accepts inbound P2P connections (`network.listen_addr` is set, which is the default).\n3. Your node's mempool is active (node is synced near the chain tip).\n\nAll default configurations are affected.\n\n### Summary\n\nA single unauthenticated P2P peer can monopolize all 25 inbound mempool download/verification slots (`MAX_INBOUND_CONCURRENCY`) by advertising fake transaction IDs. While the slots are occupied, all other inbound transactions from honest peers and local RPC `sendrawtransaction` calls are rejected with `MempoolError::FullQueue`. The attacker peer is never scored for misbehavior and is not disconnected, allowing sustained denial of mempool admission.\n\n### Details\n\nThe mempool download/verification pipeline at `zebrad/src/components/mempool/downloads.rs` uses a single bounded pool of 25 concurrent tasks. Three architectural gaps combine to produce the vulnerability:\n\n1. No per-peer accounting: the 25 slots are shared across all peers with no cap on how many a single peer can hold.\n2. No overload signaling: when `FullQueue` is returned, the inbound service at `zebrad/src/components/inbound.rs` maps it to `Response::Nil`, hiding the overload from the peer connection layer. The existing `handle_inbound_overload` disconnection logic never fires.\n3. No misbehavior attribution: peer identity is not carried through the `Gossip` type into the download pipeline, so verification failures cannot be attributed to the originating peer.\n\nThe attacker sends `inv` messages advertising fake transaction IDs. Zebra queues download tasks for each ID. The attacker stays silent; each slot is held until the `TRANSACTION_DOWNLOAD_TIMEOUT` (20 seconds) fires. The attacker periodically sends fresh `inv` waves to re-fill slots as they expire.\n\nTwo additional slot-holding techniques have been independently demonstrated: invalid-prevout transactions that park in `AwaitOutput` for 60 seconds, and expensive shielded proof verification with auth-variant cache bypass. All three techniques are addressed by the same per-peer accounting fix.\n\n### Patches\n\nzebrad 4.5.0\n\nThe fix adds per-peer queue accounting to the mempool download pipeline. A single peer is limited to a fraction of `MAX_INBOUND_CONCURRENCY` (e.g., 5 slots out of 25). `FullQueue` is surfaced as an overload signal to the peer connection layer. Peer identity is plumbed through the `Gossip` type for misbehavior attribution.\n\n### Workarounds\n\nThere is no complete configuration-level workaround. Reducing `network.peerset_initial_target_size` limits the total inbound peer count but does not prevent a single peer from holding all mempool slots.\n\n### Impact\n\nMempool transaction admission is denied for all honest peers and local RPC clients while the attack is sustained. Block validation and chain synchronization continue normally. The attacker needs only one TCP connection and minimal bandwidth (~1 KB/s of fake `inv` messages). The node recovers immediately when the attacker stops. This does not affect consensus, funds, or on-disk state.\n\n### Credit\n\nReported by `@dingledropper` via a private GitHub Security Advisory submission.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "zebrad"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.5.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 4.4.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-4fc2-h7jh-287c"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/ZcashFoundation/zebra"
}, {
"type" : "WEB",
"url" : "https://github.com/ZcashFoundation/zebra/blob/d4cd662c716382f6397d2a730148025a1ca79fec/zebrad/src/components/mempool/downloads.rs#L82"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-02T19:39:02Z",
"nvd_published_at" : null
}
}