CVE-2026-34066
nimiq-blockchain provides persistent block storage for Nimiq's Rust …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50
- github.com/nimiq/core-rs-albatross/pull/3656
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg
- github.com/advisories/GHSA-j99g-7rqw-q9jg
- nvd.nist.gov/vuln/detail/CVE-2026-34066
- nvd.nist.gov/vuln/detail/CVE-2026-34066
- cve.org/CVERecord?id=CVE-2026-34066
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.