Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. zebra-chain
  4. ›
  5. CVE-2026-34202

CVE-2026-34202: Zebra node crash — V5 transaction hash panic (P2P reachable)

March 27, 2026

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.

References

  • github.com/ZcashFoundation/zebra
  • github.com/ZcashFoundation/zebra/releases/tag/v4.3.0
  • github.com/ZcashFoundation/zebra/security/advisories/GHSA-qp6f-w4r3-h8wg
  • github.com/advisories/GHSA-qp6f-w4r3-h8wg
  • nvd.nist.gov/vuln/detail/CVE-2026-34202
  • zfnd.org/zebra-4-3-0-critical-security-fixes-zip-235-support-and-performance-improvements

Code Behaviors & Features

Detect and mitigate CVE-2026-34202 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 6.0.1

Fixed versions

  • 6.0.1

Solution

Upgrade to version 6.0.1 or above.

Impact 8.6 HIGH

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

Learn more about CVSS

Weakness

  • CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine
  • CWE-94: Improper Control of Generation of Code ('Code Injection')

Source file

cargo/zebra-chain/CVE-2026-34202.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 28 Mar 2026 12:19:59 +0000.