CVE-2026-34067
Last modified
CVE-2026-34067 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. 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())`. EPSS estimates a 0.32% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nimiq | Nimiq Proof-Of-Stake | < 1.3.0 |
References
- https://github.com/nimiq/core-rs-albatross/pull/3659Issue Tracking, Patch
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jmPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-34067?
How severe is CVE-2026-34067?
How do I fix CVE-2026-34067?
Are you affected by CVE-2026-34067?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST