Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-54496: Missing copy constraint in halo2_gadgets variable-base scalar multiplication allows under-constrained base, breaking Orchard Action circuit soundness

CriticalCVSS 9.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: halo2_gadgets (crates.io) 0.5.0; orchard (crates.io) 0.14.0; zcash_primitives (crates.io) 0.28.0.

Low priority for now. Upgrade to halo2_gadgets (crates.io) 0.5.0; orchard (crates.io) 0.14.0; zcash_primitives (crates.io) 0.28.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 17, 2026
Updated
Jul 17, 2026
EPSS
0.3% · 24th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-54496

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • zcash halo2_gadgets

    • < 0.5.0affected
  • zcash librustzcash

    • < 0.28.0affected
  • zcash orchard

    • < 0.14.0affected
  • zcash zcash

    • < 6.20.0affected
  • ZcashFoundation zebra

    • < 5.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iohalo2_gadgetsbefore 0.5.00.5.0
crates.ioorchardbefore 0.14.00.14.0
crates.iozcash_primitivesbefore 0.28.00.28.0
crates.iozebradbefore 5.0.05.0.0

Other highest-scoring records for the same primary product.

  • CVE-2026-52735ZEBRA: Consensus divergence via P2SH sigop undercount in pure-Rust disabled-opcode parser
    37Monitor
  • CVE-2026-123560Zebra before 7.0.0 Sync Denial of Service via Forged Checkpoint Block Body
    34Monitor
  • CVE-2026-123559Zebra before 7.0.0 Denial of Service via Quadratic Sighash Computation
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-44499May 8, 2026 · ZEBRA: Permanent Block Discovery Halt via Gossip Queue Saturation and Syncer Poisoning
    34Monitor
  • Later →CVE-2026-52731Aug 18, 2026 · ZEBRA: Full node denial of service via non-ASCII LongPollId in getblocktemplate
    26Monitor
  • Later →CVE-2026-52732Aug 18, 2026 · ZEBRA: Mempool transaction admission denial via single-peer inbound queue saturation
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
crates.io:halo2_gadgets0.5.0Package registry (OSV)
crates.io:orchard0.14.0Package registry (OSV)
crates.io:zcash_primitives0.28.0Package registry (OSV)
crates.io:zebrad5.0.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-10442277 days apartZebra before 6.3.0 Block Sync Denial of Service via Coinbase scriptSig Rewrite
    34Monitor
  • CVE-2026-10441977 days apartZebra before 6.3.0 Honest Peer Banning via Far-Ahead FindBlocks Hashes
    25Monitor
  • CVE-2026-10936587 days apartZebra before 6.4.0 Denial of Service via Same-Hash Forged Block Bodies
    25Monitor
  • CVE-2026-5273732 days apartZEBRA: Sync restart poisoning from single unauthenticated peer via above-lookahead block
    21Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
None
Integrity impact
High
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L

nvd-secondary

References

All records