| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-264v-m8fm-76jm | nimiq-transaction: Panic via `HistoryTreeProof` length mismatch |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 24 Apr 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nimiq
Nimiq nimiq Proof-of-stake |
|
| CPEs | cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:* | |
| Vendors & Products |
Nimiq
Nimiq nimiq Proof-of-stake |
Thu, 23 Apr 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch | |
| Weaknesses | CWE-617 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-23T14:17:59.735Z
Reserved: 2026-03-25T16:21:40.867Z
Link: CVE-2026-34067
Updated: 2026-04-23T14:17:55.804Z
Status : Analyzed
Published: 2026-04-22T21:17:07.760
Modified: 2026-04-24T17:12:48.173
Link: CVE-2026-34067
No data.
OpenCVE Enrichment
No data.
Github GHSA