# zebrad vulnerable to full node denial of service via crafted Sapling receiver in z_listunifiedreceivers Advisory record · `GHSA-c8w6-x74f-vmg3` - **Identifiers:** `GHSA-c8w6-x74f-vmg3` · `CVE-2026-104434` - **State:** Confirmed - **Severity:** CVSS 7.1 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-248](https://cwe.mitre.org/data/definitions/248.html) · [CWE-617](https://cwe.mitre.org/data/definitions/617.html) · [CWE-754](https://cwe.mitre.org/data/definitions/754.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-248](https://agentprime.io/advisories/tag/cwe-248.md) · [CWE-754](https://agentprime.io/advisories/tag/cwe-754.md) - **Published:** 2 Jul 2026 - **Updated:** 3 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 2 Jul 2026, 19:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `zebra-rpc` (crates.io): affected `<8.0.0`; fixed in `8.0.0` - `zebrad` (crates.io): affected `<4.5.0`; fixed in `4.5.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Affected: zebrad versions up to and including 4.4.1, and zebra-rpc before 8.0.0, where a crafted Sapling receiver in a Unified Address passed to z_listunifiedreceivers causes a panic. An attacker needs to authenticate to the RPC endpoint, which with default cookie auth means local access to the cookie file, or network access to the RPC port if cookie auth is disabled. A single request then aborts the whole node process. Upgrade zebrad to 4.5.0 and zebra-rpc to 8.0.0; until then, disable the RPC server or keep cookie auth enabled and restrict access to the cookie file. Written 3 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0031, the 23rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:24 UTC: First seen by agentprime - 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c8w6-x74f-vmg3) ## Sources - [GitHub Advisory Database: GHSA-c8w6-x74f-vmg3](https://github.com/advisories/GHSA-c8w6-x74f-vmg3) - [OSV: GHSA-c8w6-x74f-vmg3](https://osv.dev/vulnerability/GHSA-c8w6-x74f-vmg3) - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .