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.
CVE-2026-52735
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(medium)
- EG Risk
- 57(Track)EG Risk 57/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity93% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 18, 2026
Advisory Details (3)
Auto-updated Aug 23, 2026Consensus divergence via P2SH sigop undercount in pure-Rust disabled-opcode parser · Advisory · ZcashFoundation/zebra · GitHub
https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-gf9r-m956-97qxZebra 4.5.0
Patch available: ZcashFoundation/zebra v4.5.0
https://github.com/ZcashFoundation/zebra/releases/tag/v4.5.0commit 1440b43ca7df (ZcashFoundation/zebra)
Patch available: ZcashFoundation/zebra v4.5.0 (contains commit 1440b43ca7df)
https://github.com/ZcashFoundation/zebra/commit/1440b43ca7df59aca948090d45117557b217a6cdVendor Advisories for CVE-2026-52735(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| zebrad | — | 4.5.0 | — |
| zebra-script | — | 7.0.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:23 UTCEG score recompute
- 2026-08-24 10:16 UTCEG score recompute
- 2026-08-23 03:39 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:27 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 00:36 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 04:02 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 19:54 UTCEG score recompute
- 2026-08-18 19:29 UTCEG score recompute▲ 9.30
- 2026-08-18 19:29 UTCMITRE cvelistV5CVSS v3 → 9.3 · CVSS v4 → 9.3
- 2026-08-01 17:17 UTCEG score recompute
- 2026-07-26 13:03 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-02 20:07 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-52735?
When was CVE-2026-52735 disclosed?
Is CVE-2026-52735 actively exploited?
What is the CVSS score of CVE-2026-52735?
How do I remediate CVE-2026-52735?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52735
Is Your Infrastructure Affected by CVE-2026-52735?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.