CVE-2026-52735
CRITICALDescription
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, Zebra can accept a block that zcashd rejects because the P2SH signature-operation counter undercounts redeem scripts containing a disabled opcode followed by signature opcodes. In zebra-script/src/lib.rs, p2sh_input_sigop_count used the pure-Rust script::Code::sig_op_count path, whose try_fold parser stops at disabled opcodes such as OP_CODESEPARATOR and returns only the partial count accumulated before the error. The zcashd reference implementation continues static signature-operation counting through disabled opcodes, so an attacker can broadcast P2SH spends that Zebra counts below MAX_BLOCK_SIGOPS while zcashd counts above the 20,000-operation limit. If a Zebra miner includes those transactions, Zebra validators accept the block while zcashd validators reject it, creating a consensus chain split that affects network integrity and availability without requiring the attacker to produce a block. This issue is fixed in version 4.5.0.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 21% of all known CVEs.
References
Related Vulnerabilities
Other CWE-684 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-5363 | High | 7.5 | 3.3% | - | Fix |
| CVE-2025-47227 | High | 7.5 | 2.1% | - | - |
| CVE-2020-11054 | Low | 3.5 | 1.5% | - | Fix |
| CVE-2026-34478 | High | 7.5 | 1.0% | - | Fix |
| CVE-2023-24845 | Critical | 9.1 | 0.7% | - | - |
| CVE-2024-50357 | Critical | 9.8 | 0.6% | - | - |
Common questions
How do I fix CVE-2026-52735?
No published fix for CVE-2026-52735 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-52735 being actively exploited?
Not that we know of. CVE-2026-52735 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.29% is the estimated probability that it will be exploited in the next 30 days. That is higher than 21% of all scored CVEs.
How severe is CVE-2026-52735?
CVE-2026-52735 has a CVSS v4 base score of 9.3, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-52735
Markdown
[](https://tridentstack.com/cve/CVE-2026-52735)HTML
<a href="https://tridentstack.com/cve/CVE-2026-52735"><img src="https://tridentstack.com/cve/badge/CVE-2026-52735.svg" alt="CVE-2026-52735"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-18.