Home

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.

PUBLISHED Reserved 2026-03-25 | Published 2026-04-22 | Updated 2026-04-23 | Assigner GitHub_M




MEDIUM: 5.3CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

Problem types

CWE-20: Improper Input Validation

CWE-617: Reachable Assertion

CWE-754: Improper Check for Unusual or Exceptional Conditions

Product status

< 1.3.0
affected

References

github.com/...atross/security/advisories/GHSA-j99g-7rqw-q9jg

github.com/nimiq/core-rs-albatross/pull/3656

github.com/...ommit/6f5511309c199d84b012fe6b9aba7e5582892c50

github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0

cve.org (CVE-2026-34066)

nvd.nist.gov (CVE-2026-34066)

Download JSON