CVE-2026-34202 | ZcashFoundation zebra/zebra-chain prior 4.3.0 Transaction ID special elements used in a template engine

VDB-354402 · CVE-2026-34202 · GCVE-0-2026-34202 ZCASHFOUNDATION ZEBRA/ZEBRA-CHAIN PRIOR 4.3.0 TRANSACTION ID SPECIAL ELEMENTS USED IN A TEMPLATE ENGINE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 2.37+ Summaryinfo A vulnerability was found in ZcashFoundation zebra and zebra-chain. It has been declared as problematic. This issue affects some unknown processing of the component Transaction ID Handler. The manipulation results in improper neutralization of special elements used in a template engine. This vulnerability is reported as CVE-2026-34202. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component. Detailsinfo A vulnerability classified as problematic has been found in ZcashFoundation zebra and zebra-chain. Affected is some unknown processing of the component Transaction ID Handler. The manipulation with an unknown input leads to a improper neutralization of special elements used in a template engine vulnerability. CWE is classifying the issue as CWE-1336. The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. This is going to have an impact on availability. CVE summarizes: ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.0 and zebra-chain version 6.0.1, a vulnerability in Zebra's transaction processing logic allows a remote, unauthenticated attacker to cause a Zebra node to panic (crash). This is triggered by sending a specially crafted V5 transaction that passes initial deserialization but fails during transaction ID calculation. This issue has been patched in zebrad version 4.3.0 and zebra-chain version 6.0.1. The advisory is available at github.com. This vulnerability is traded as CVE-2026-34202 since 03/26/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1221 by the MITRE ATT&CK project. Upgrading to version 4.3.0 eliminates this vulnerability. Productinfo Vendor ZcashFoundation Name zebra zebra-chain Website Product: https://github.com/ZcashFoundation/zebra/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Improper neutralization of special elements used in a template engine CWE: CWE-1336 / CWE-791 / CWE-790 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: zebra/zebra-chain 4.3.0 Timelineinfo 03/26/2026 CVE reserved 03/31/2026 +4 days Advisory disclosed 03/31/2026 +0 days VulDB entry created 03/31/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-34202 (🔒) GCVE (CVE): GCVE-0-2026-34202 GCVE (VulDB): GCVE-100-354402 Entryinfo Created: 03/31/2026 17:02 Changes: 03/31/2026 17:02 (65) Complete: 🔍 Cache ID: 99:A9C:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸