~ / search / GHSA-264v-m8fm-76jm

GHSA-264v-m8fm-76jm

nimiq-transaction: Panic via `HistoryTreeProof` length mismatch

Source: GitHub Advisory Database (reviewed) Low CVE-2026-34067

Packages

EcosystemPackageAffectedFixed in
crates.io nimiq-transaction <= 0.2.0 no fix listed

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact `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. ### Patches [The patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a) is included as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0). ### Workarounds No known workarounds know.

References

External links from the advisory. They lead to third-party sites.