{"answers":{"affected":"4 open source packages ship an affected version, including zebra-network and zebrad.","exploited":"There is no known exploitation of CVE-2026-52829 in the wild and no public exploit code.","fix":"Upgrade zebra-network to 7.0.0 or later.","what":"CVE-2026-52829 is a high-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-52829 and fix it if it is affected.\n\nWhat it is: CVE-2026-52829 is a high-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-52829 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zebra-network (crates.io): affected all versions; fixed in 7.0.0\n- zebra-network (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-52829/ (Markdown: https://insights.sbomify.com/CVE-2026-52829/index.md)","id":"CVE-2026-52829","markdown":"https://insights.sbomify.com/CVE-2026-52829/index.md","name":"CVE-2026-52829","record":{"aliases":["GHSA-63wg-wjjj-7cp8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Zcash node","requires_auth":"none","summary":"An unauthenticated peer can crash a synced Zebra node by triggering an assertion failure during mempool misbehavior updates.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-617","name":"Reachable Assertion"}],"description":"ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, an unauthenticated IPv4 peer can deterministically terminate a synced Zebra node using the default Linux dual-stack listener configuration. The handshake path canonicalized an IPv4-mapped IPv6 PeerSocketAddr such as ::ffff:127.0.0.1 to plain IPv4 before storing it through MetaAddr::new_connected, but the mempool misbehavior path forwarded the raw transient address to MetaAddrChange::UpdateMisbehavior. In zebra-network/src/meta_addr.rs, apply_to_meta_addr then compared the canonical address-book entry with the raw update address and reached its unexpected address mismatch assertion. After the misbehavior batch flush, panic equals abort terminated zebrad; the peer only needed to complete a P2P handshake and advertise an invalid mempool 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: IPv4-Mapped Mempool Misbehavior Update Aborts Zebra Address Book","id":"CVE-2026-52829","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":"fast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protection","id":"CVE-2026-52830"},"packages":[{"ecosystem":"crates.io","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-network","purl":null,"source":"GHSA-63wg-wjjj-7cp8"},{"ecosystem":"crates.io","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-network","purl":"pkg:cargo/zebra-network","source":"GHSA-63wg-wjjj-7cp8"},{"ecosystem":"crates.io","fixed":["4.5.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":null,"source":"GHSA-63wg-wjjj-7cp8"},{"ecosystem":"crates.io","fixed":["4.5.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":"pkg:cargo/zebrad","source":"GHSA-63wg-wjjj-7cp8"}],"prev":{"headline":"Kimai: ExportTemplate CRUD Missing Authorization Check Allows Unauthorized TEAMLEAD Access","id":"CVE-2026-52828"},"products":["zebra"],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["ZcashFoundation"]},"summary":"An unauthenticated peer can crash a synced Zebra node by triggering an assertion failure during mempool misbehavior updates.","url":"https://insights.sbomify.com/CVE-2026-52829/"}