CVE-2026-54496
ZEBRA vulnerability
- Published17 Jul 2026
Description
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad 5.0.0, halo2_gadgets 0.5.0, orchard 0.14.0, zcash_primitives 0.28.0, and zcashd 6.20.0, the variable-base scalar multiplication gadget in halo2_gadgets/src/ecc/chip/mul/incomplete.rs used assign_advice() for the base point without a copy constraint tying it to the actual base, allowing a malicious prover to produce a valid proof for an Orchard Action with an under-constrained base point and bypass the diversified-address-integrity check that binds pk_d, g_d, ivk, the nullifier (nf), and the spend validating key (ak) to the note being spent. This issue is fixed in zebrad 5.0.0, halo2_gadgets 0.5.0, orchard 0.14.0, zcash_primitives 0.28.0, and zcashd 6.20.0.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:LRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/ZcashFoundation/zebra/releases/tag/v5.0.0
- https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-ww9q-8r59-xv46
- https://github.com/zcash/halo2/releases/tag/halo2_gadgets-0.5.0
- https://github.com/zcash/librustzcash/releases/tag/zcash_primitives-0.28.0
- https://github.com/zcash/orchard/releases/tag/0.14.0
- https://github.com/zcash/zcash/releases/tag/v6.20.0
- https://zfnd.org/zebra-4-5-3-and-5-0-0-emergency-soft-fork-and-nu6-2-activation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-54496 being actively exploited?
CVE-2026-54496 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.32%.
How severe is CVE-2026-54496?
CVE-2026-54496 has a CVSS 3.1 base score of 9.3, rated critical. EPSS estimates a 0.32% probability of exploitation.
How do I fix CVE-2026-54496?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-54496 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.