Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nimiq | Nimiq Proof-Of-Stake | < 1.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7ePatch
- https://github.com/nimiq/core-rs-albatross/pull/3656Issue TrackingPatch
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0Release Notes
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9PatchVendor Advisory
FAQ
What is CVE-2026-34066?
CVE-2026-34066 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 `HistoricTra...
How severe is CVE-2026-34066?
CVE-2026-34066 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-34066?
Check the references section above for vendor advisories and patch information. Affected products include: Nimiq Nimiq Proof-Of-Stake.