{"answers":{"affected":"4 open source packages ship an affected version, including zebra-script and zebrad. It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-41583 in the wild and no public exploit code.","fix":"Upgrade zebra-script to 5.0.2 or later.","what":"CVE-2026-41583 is a critical vulnerability in ZcashFoundation zebra, published on 8 May 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-41583 and fix it if it is affected.\n\nWhat it is: CVE-2026-41583 is a critical vulnerability in ZcashFoundation zebra, published on 8 May 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-41583 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zebra-script (crates.io): affected all versions; fixed in 5.0.2\n- zebra-script (crates.io): affected all versions; fixed in 5.0.2\n- zebrad (crates.io): affected all versions; fixed in 4.3.1\n- zebrad (crates.io): affected all versions; fixed in 4.3.1\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-41583/ (Markdown: https://insights.sbomify.com/CVE-2026-41583/index.md)","id":"CVE-2026-41583","markdown":"https://insights.sbomify.com/CVE-2026-41583/index.md","name":"CVE-2026-41583","record":{"aliases":["GHSA-8m29-fpq5-89jj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Zcash node software","requires_auth":"none","summary":"Zcash nodes may accept invalid blocks due to incorrect sighash validation, causing consensus splits with other nodes and potential network disruption.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zebra-script","vendor":"zfnd"},{"product":"zebrad","vendor":"zfnd"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-573","name":"Improper Following of Specification by Caller"}],"description":"ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and prior to zebra-script version 5.0.2, after a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade. Zebra nodes could thus accept and eventually mine a block that would be considered invalid by zcashd nodes, creating a consensus split between Zebra and zcashd nodes. In a similar vein, for V4 transactions, Zebra mistakenly used the \"canonical\" hash type when computing the sighash while zcashd (correctly per the spec) uses the raw value, which could also crate a consensus split. This issue has been patched in zebrad version 4.3.1 and zebra-script version 5.0.2.","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: Consensus Divergence in Transparent Sighash Hash-Type Handling","id":"CVE-2026-41583","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"ZEBRA: rk Identity Point Panic in Transaction Verification","id":"CVE-2026-41584"},"packages":[{"ecosystem":"crates.io","fixed":["5.0.2"],"introduced":["0"],"last_affected":[],"package":"zebra-script","purl":null,"source":"GHSA-8m29-fpq5-89jj"},{"ecosystem":"crates.io","fixed":["5.0.2"],"introduced":["0"],"last_affected":[],"package":"zebra-script","purl":"pkg:cargo/zebra-script","source":"GHSA-8m29-fpq5-89jj"},{"ecosystem":"crates.io","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":null,"source":"GHSA-8m29-fpq5-89jj"},{"ecosystem":"crates.io","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":"pkg:cargo/zebrad","source":"GHSA-8m29-fpq5-89jj"}],"prev":{"headline":"countly-server: Unauthenticated Path Traversal via Public Image and Screenshot Routes Leads to Read Internal Files","id":"CVE-2026-41582"},"products":["zebra"],"published":"2026-05-08","related":[{"cvss_score":9.3,"headline":"ZEBRA: Consensus Divergence in Transparent Sighash Hash-Type Handling due to Stale Buffer","id":"CVE-2026-44497","kev_date_added":null,"published":"2026-05-08"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-05-08","vendors":["ZcashFoundation"]},"summary":"Zcash nodes may accept invalid blocks due to incorrect sighash validation, causing consensus splits with other nodes and potential network disruption.","url":"https://insights.sbomify.com/CVE-2026-41583/"}