What’s Vulnerable › Vulnerabilities

CVE-2026-34067: nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch

• Severity: medium (CVSS 6.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-04-22 · updated 2026-10-26
• Weakness: CWE-617

Description

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.

Affected products

• nimiq-transaction: before 1.3.0 — fixed in 1.3.0

How to fix

Upgrade to a fixed version: nimiq-transaction 1.3.0. Check the vendor advisory for mitigations.

References

• https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a
• https://github.com/nimiq/core-rs-albatross/pull/3659
• https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
• https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm

Get alerted when CVE-2026-34067 or the next vulnerability affects your stack