CVE-2026-34067
nimiq-transaction provides the transaction primitive to be used in …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a
- github.com/nimiq/core-rs-albatross/pull/3659
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm
- github.com/advisories/GHSA-264v-m8fm-76jm
- nvd.nist.gov/vuln/detail/CVE-2026-34067
- nvd.nist.gov/vuln/detail/CVE-2026-34067
- cve.org/CVERecord?id=CVE-2026-34067
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.