CVE-2026-34067: nimiq-transaction: Panic via `HistoryTreeProof` length mismatch
(updated )
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.
References
- github.com/advisories/GHSA-264v-m8fm-76jm
- 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
- nvd.nist.gov/vuln/detail/CVE-2026-34067
Code Behaviors & Features
Detect and mitigate CVE-2026-34067 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →