Vulnerability Description
nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nimiq | Nimiq Proof-Of-Stake | < 1.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033Patch
- https://github.com/nimiq/core-rs-albatross/pull/3659Issue TrackingPatch
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0Release Notes
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76PatchVendor Advisory
FAQ
What is CVE-2026-34067?
CVE-2026-34067 is a vulnerability with a CVSS score of 3.1 (LOW). nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != p...
How severe is CVE-2026-34067?
CVE-2026-34067 has been rated LOW with a CVSS base score of 3.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-34067?
Check the references section above for vendor advisories and patch information. Affected products include: Nimiq Nimiq Proof-Of-Stake.