| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Zcash zcashd up to 6.11.x. This vulnerability affects unknown code of the component Transaction Handler. The manipulation leads to security check. This vulnerability is uniquely identified as CVE-2026-35679. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Zcash zcashd up to 6.11.x. This issue affects an unknown code of the component Transaction Handler. The manipulation with an unknown input leads to a security check vulnerability. Using CWE to declare the problem leads to CWE-358. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. Impacted is integrity. The summary by CVE is:
Zcash zcashd before 6.12.0 allows invalid transactions to be accepted under certain conditions, which potentially could have resulted in the draining of user funds from the Sprout pool. It was sometimes not verifying Sprout proofs.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-35679 since 04/05/2026. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1211 for this issue.
Upgrading to version 6.12.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch db969c63f48f0f9fc518112ed0b7ace1af78b9d0 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.5
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Security checkCWE: CWE-358
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: zcashd 6.12.0
Patch: db969c63f48f0f9fc518112ed0b7ace1af78b9d0
Timeline
04/05/2026 CVE reserved04/06/2026 Advisory disclosed
04/06/2026 VulDB entry created
04/06/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-35679 (🔒)
GCVE (CVE): GCVE-0-2026-35679
GCVE (VulDB): GCVE-100-355457
Entry
Created: 04/06/2026 08:04Changes: 04/06/2026 08:04 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.