https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T18:30:58.808845+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-292760 EUVD-2026-292760 2026-10-07T18:30:58.811775+00:00 EUVD-2026-292760 https://cve.radiocsirt.org/vuln/fkie_cve-2026-34067 fkie_cve-2026-34067 2026-10-07T18:30:58.811833+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-264v-m8fm-76jm GHSA-264v-m8fm-76jm — nimiq-transaction: Panic via `HistoryTreeProof` length mismatch 2026-10-07T18:30:58.811931+00:00

Affected: crates.io: nimiq-transaction

### Impact `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.

### Patches [The patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a) is included as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0).

### Workarounds No known workarounds know.