{"answers":{"affected":"4 open source packages ship an affected version, including zebra-state and zebrad.","exploited":"There is no known exploitation of CVE-2026-52739 in the wild and no public exploit code.","fix":"Upgrade zebra-state to 7.0.0 or later.","what":"CVE-2026-52739 is a medium-severity denial of service vulnerability in ZcashFoundation zebra, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52739 and fix it if it is affected.\n\nWhat it is: CVE-2026-52739 is a medium-severity denial of service vulnerability in ZcashFoundation zebra, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52739 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zebra-state (crates.io): affected all versions; fixed in 7.0.0\n- zebra-state (crates.io): affected all versions; fixed in 7.0.0\n- zebrad (crates.io): affected all versions; fixed in 4.5.0\n- zebrad (crates.io): affected all versions; fixed in 4.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-52739/ (Markdown: https://insights.sbomify.com/CVE-2026-52739/index.md)","id":"CVE-2026-52739","markdown":"https://insights.sbomify.com/CVE-2026-52739/index.md","name":"CVE-2026-52739","record":{"aliases":["GHSA-hhm7-qrv5-h4r6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Zcash node software","requires_auth":"none","summary":"A malicious block producer can crash the Zebra Zcash node by including duplicate shielded transactions in consecutive blocks, causing a process abort.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, a malicious block producer can terminate zebrad by placing the same shielded transaction in a non-finalized parent block and its child. In zebra-state/src/service/non_finalized_state/chain.rs, Chain::push originally inserted the transaction hash into tx_loc_by_hash and asserted uniqueness before updating shielded data and running the duplicate Sprout, Sapling, or Orchard nullifier checks. The repeated transaction therefore reached the transactions must be unique within a single chain assertion before contextual validation could reject it cleanly. Zebra release builds use panic equals abort, so the reachable assertion terminates the entire process; exploitation requires either two consecutive attacker-mined blocks or an attacker-mined child immediately after an honest block includes the attacker's shielded transaction. This issue is fixed in version 4.5.0.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ZEBRA: Repeated Non-Finalized Shielded Transaction Aborts Zebra Before Duplicate-Nullifier Rejection","id":"CVE-2026-52739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"GoCD is vulnerable to pipeline template view API authorization bypass","id":"CVE-2026-52740"},"packages":[{"ecosystem":"crates.io","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-state","purl":null,"source":"GHSA-hhm7-qrv5-h4r6"},{"ecosystem":"crates.io","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-state","purl":"pkg:cargo/zebra-state","source":"GHSA-hhm7-qrv5-h4r6"},{"ecosystem":"crates.io","fixed":["4.5.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":null,"source":"GHSA-hhm7-qrv5-h4r6"},{"ecosystem":"crates.io","fixed":["4.5.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":"pkg:cargo/zebrad","source":"GHSA-hhm7-qrv5-h4r6"}],"prev":{"headline":"ZEBRA: Finalized address balance credit-first overflow on consensus-valid blocks","id":"CVE-2026-52738"},"products":["zebra","zebra-state"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["ZcashFoundation"]},"summary":"A malicious block producer can crash the Zebra Zcash node by including duplicate shielded transactions in consecutive blocks, causing a process abort.","url":"https://insights.sbomify.com/CVE-2026-52739/"}