Skip to content

CVE-2026-34066 nimiq-blockchain: Peer-triggerable panic during history sync

MediumCVSS 5.3 EPSS 0.25%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, HistoryStore::put_historic_txns uses an assert! to enforce invariants about HistoricTransaction.block_number (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the history: &[HistoricTransaction] input passed into Blockchain::push_history_sync, and a malformed history list can violate these invariants and trigger a panic. extend_history_sync calls this.history_store.add_to_history(..) before comparing the computed history root against the macro block header (block.history_root()), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
crates.io nimiq-blockchain(crates.io) <= 0.2.0 after 0.2.0 Fixed
nimiq proof-of-stake < 1.3.0 1.3.0 Fixed
nimiq-blockchain = < 1.3.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
nimiq-blockchain = < 1.3.0 No fix listed
crates.io nimiq-blockchain(crates.io) <= 0.2.0 No fix listed
nimiq proof-of-stake < 1.3.0 1.3.0

References