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.
Affected products
nimiq: nimiq proof-of-stake
References4
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99… PatchVendor Advisory
- github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012f… Patch
- github.com/nimiq/core-rs-albatross/pull/3656 Issue TrackingPatch
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 Release Notes
Metrics
- CVSS 3.1
-
5.3
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 15 · as of 13 November 2026
- CWE
- CWE-20CWE-617CWE-754
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.