{"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-44497 in the wild and no public exploit code.","fix":"Upgrade zebra-script to 6.0.0 or later.","what":"CVE-2026-44497 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-44497 and fix it if it is affected.\n\nWhat it is: CVE-2026-44497 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-44497 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zebra-script (crates.io): affected all versions; fixed in 6.0.0\n- zebra-script (crates.io): affected all versions; fixed in 6.0.0\n- zebrad (crates.io): affected all versions; fixed in 4.4.0\n- zebrad (crates.io): affected all versions; fixed in 4.4.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-44497/ (Markdown: https://insights.sbomify.com/CVE-2026-44497/index.md)","id":"CVE-2026-44497","markdown":"https://insights.sbomify.com/CVE-2026-44497/index.md","name":"CVE-2026-44497","record":{"aliases":["GHSA-gq4h-3grw-2rhv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Zcash node","requires_auth":"none","summary":"Attackers can cause consensus divergence between Zebra and zcashd nodes by exploiting stale buffer handling in sighash computation.","user_interaction":"not_required","vuln_class":"other"},"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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.4.0 and prior to zebra-script version 6.0.0, the fix for CVE-2026-41583 introduced a separate issue due to insufficient error handling of the case where the sighash type is invalid, during sighash computation. Instead of returning an error, the normal flow would resume, and the input sighash buffer would be left untouched. In scenarios where a previous signature validation could leave a valid sighash in the buffer, an invalid hash-type could be incorrectly accepted, which would create a consensus split between Zebra and zcashd nodes. This issue has been patched in zebrad version 4.4.0 and zebra-script version 6.0.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: Consensus Divergence in Transparent Sighash Hash-Type Handling due to Stale Buffer","id":"CVE-2026-44497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"ZEBRA: Block Validator Undercounts Coinbase and P2SH Sigops","id":"CVE-2026-44498"},"packages":[{"ecosystem":"crates.io","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-script","purl":null,"source":"GHSA-gq4h-3grw-2rhv"},{"ecosystem":"crates.io","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"zebra-script","purl":"pkg:cargo/zebra-script","source":"GHSA-gq4h-3grw-2rhv"},{"ecosystem":"crates.io","fixed":["4.4.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":null,"source":"GHSA-gq4h-3grw-2rhv"},{"ecosystem":"crates.io","fixed":["4.4.0"],"introduced":["0"],"last_affected":[],"package":"zebrad","purl":"pkg:cargo/zebrad","source":"GHSA-gq4h-3grw-2rhv"}],"prev":{"headline":"Axios: Regular Expression Denial of Service (ReDoS) via Cookie Name Injection","id":"CVE-2026-44496"},"products":["zebra"],"published":"2026-05-08","related":[{"cvss_score":9.3,"headline":"ZEBRA: Consensus Divergence in Transparent Sighash Hash-Type Handling","id":"CVE-2026-41583","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":"partial"},"state":"PUBLISHED","updated":"2026-05-08","vendors":["ZcashFoundation"]},"summary":"Attackers can cause consensus divergence between Zebra and zcashd nodes by exploiting stale buffer handling in sighash computation.","url":"https://insights.sbomify.com/CVE-2026-44497/"}