CVE-2026-34066

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.

CVSS 3.1

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

EPSS

0.2% chance of exploitation in the next 30 days; higher than 15% of CVEs (scores of 2026-10-26)

CWEs

CWE-20, CWE-617, CWE-754

Published

2026-04-22

Modified

2026-10-26

Record from

the NVD, synced 2026-10-26

Affected

• nimiq:nimiq_proof-of-stake

Packages (OSV)

References

• https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50
• https://github.com/nimiq/core-rs-albatross/pull/3656
• https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
• https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg

Check your stackJSON