CVE-2026-34067: nimiq-transaction · Reachable Assertion
Affects nimiq-transactionSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low : upgrade to 1.3.0 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade nimiq-transaction and nimiq/nimiq-transaction to 1.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nimiqnimiq-transaction | Affected
| Fixed in
|
crates.ionimiq/nimiq-transactionpkg:cargo/nimiq/nimiq-transactionOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to nimiq-transaction version 1.3.0 or later, where the assertion panic is fixed. No known workarounds exist. Since this is a library vulnerability, ensure that all dependent software using nimiq-transaction is updated accordingly.
Description
CVE-2026-34067 is a low-severity vulnerability in the nimiq-transaction Rust library used by Nimiq. Before version 1.3.0, the function HistoryTreeProof::verify contains an assertion that panics if a malformed proof has mismatched lengths between history and positions arrays. Since the proof data is attacker-controlled from untrusted peer-to-peer network responses, a malicious actor could cause the application to crash by sending a crafted proof with length mismatch. The issue is fixed in version 1.3.0. No workarounds are known.
References
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm (opens in a new tab)
- github.com/nimiq/core-rs-albatross/pull/3659 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a (opens in a new tab)
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 (opens in a new tab)