ZebraApplication · Zfnd
CVE-2026-34202
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZEBRA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Zebra's transaction processing logic allows remote attackers to cause a panic by sending specially crafted V5 transactions that pass initial deserialization but fail during transaction ID calculation. This affects zebrad versions prior to 4.3.0 and zebra-chain versions prior to 6.0.1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ZebraApplication
< 4.3.0
Zebra ChainApplication
< 6.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Zebra componentRun 'zebrad --version' for the zebrad CLI binary, or check the zebra-chain library version in your dependency file (Cargo.lock, go.mod, or similar)Affected if You have zebrad < 4.3.0 or zebra-chain < 6.0.1 installed
-
Verify V5 transaction support is activeCheck the zebrad configuration file (typically ~/.zebrad/zebrad.toml or /etc/zebrad/zebrad.toml) for 'transaction' or 'v5' related settings, or examine if the node is processing Mainnet transactions where V5 transactions may be presentAffected if V5 transaction parsing or validation is enabled on your node
-
Confirm network exposureCheck if your zebra node RPC port (default 8232) or peer port (default 8233) is exposed to untrusted networks, or review firewall rules and network binding configurationAffected if The node accepts connections from untrusted or public networks
You are affected if you run zebrad < 4.3.0 or zebra-chain < 6.0.1 AND have V5 transaction support enabled AND the node is network-accessible to remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.3.06.0.1
Upgrade zebrad to version 4.3.0 or later and zebra-chain to version 6.0.1 or later to patch the vulnerability.
zebrad 4.3.0 and zebra-chain 6.0.1
- Upgrade zebrad (Zebra node) to version 4.3.0 or later
- Upgrade zebra-chain library to version 6.0.1 or later
- Restart the Zebra node to apply the changes
- Verify the upgrade was successful by checking the zebrad version (e.g., zebrad -V)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Zebra
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data