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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a Patch
- https://github.com/nimiq/core-rs-albatross/pull/3659 Issue Tracking, Patch
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · nimiqNVD modified 2026-10-26 22:10
Affected (CPE criteria) 1
cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*
References 4
- https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a Patch
- https://github.com/nimiq/core-rs-albatross/pull/3659 Issue Tracking, Patch
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 Release Notes
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm Patch, Vendor Advisory