GHSA-264v-m8fm-76jm
nimiq-transaction: Panic via `HistoryTreeProof` length mismatch
Details
### 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.
Are you affected?
Enter the version of the package you're using.
Affected packages
0No fixed version published yet for nimiq-transaction. Pin to a known-safe version or switch to an alternative.
References
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm[WEB]
- https://nvd.nist.gov/vuln/detail/CVE-2026-34067[ADVISORY]
- https://github.com/nimiq/core-rs-albatross/pull/3659[WEB]
- https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a[WEB]
- https://github.com/nimiq/core-rs-albatross[PACKAGE]
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0[WEB]