Invalid transaction acceptance via cached incomplete verification
Published Apr 5, 2026 · Updated Apr 5, 2026
Consensus validation in Zcash zcashd before 6.12.0 allows attackers to introduce invalid Sprout transactions through newly connected tip blocks. CheckBlock set the fChecked cache flag after an initial pass with Sprout proof verification disabled, so the later strict pass skipped every check. Exploitation requires mining-pool cooperation and a transaction first seen in a new block; successful acceptance splits the chain and enables Sprout fund theft.
Summary
What happened
Consensus validation in Zcash zcashd before 6.12.0 allows attackers to introduce invalid Sprout transactions through newly connected tip blocks. CheckBlock set the fChecked cache flag after an initial pass with Sprout proof verification disabled, so the later strict pass skipped every check. Exploitation requires mining-pool cooperation and a transaction first seen in a new block; successful acceptance splits the chain and enables Sprout fund theft.
The record
- CVE
- CVE-2026-35679
- Published
- Apr 5, 2026
- Updated
- Apr 5, 2026
- Vendor
- Zcash
- Product
- zcashd
- Classifications
- CWE-358, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2026CVE publishedPublication date reported by the CVE source.
- Apr 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo