CVE-2026-34066: nimiq-blockchain: Peer-triggerable panic during history sync
(updated )
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.
References
- github.com/advisories/GHSA-j99g-7rqw-q9jg
- github.com/nimiq/core-rs-albatross
- 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
- nvd.nist.gov/vuln/detail/CVE-2026-34066
Code Behaviors & Features
Detect and mitigate CVE-2026-34066 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →