CVE-2026-34066: CWE-20: Improper Input Validation in nimiq nimiq-blockchain
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.
AI Analysis
Technical Summary
The nimiq-blockchain Rust implementation prior to version 1.3.0 contains an improper input validation vulnerability (CWE-20) in the HistoryStore::put_historic_txns function. It uses an assert to enforce that HistoricTransaction.block_number values are within expected bounds during history sync. A remote peer can supply a malformed history list to Blockchain::push_history_sync, causing the assert to fail and trigger a panic before the history root is verified against the macro block header. This results in a denial of service condition. The vulnerability is addressed by a patch included in version 1.3.0.
Potential Impact
Exploitation of this vulnerability can cause the nimiq-blockchain node to panic and crash during history synchronization, resulting in a denial of service. There is no impact on confidentiality or integrity reported. No known exploits are in the wild.
Mitigation Recommendations
Upgrade to nimiq-blockchain version 1.3.0 or later, which includes a patch that removes the unsafe assert and properly validates input before processing. No workarounds are available for affected versions prior to 1.3.0. Patch status is not explicitly stated but the fix is included in version 1.3.0, so upgrading is the recommended remediation.
CVE-2026-34066: CWE-20: Improper Input Validation in nimiq nimiq-blockchain
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The nimiq-blockchain Rust implementation prior to version 1.3.0 contains an improper input validation vulnerability (CWE-20) in the HistoryStore::put_historic_txns function. It uses an assert to enforce that HistoricTransaction.block_number values are within expected bounds during history sync. A remote peer can supply a malformed history list to Blockchain::push_history_sync, causing the assert to fail and trigger a panic before the history root is verified against the macro block header. This results in a denial of service condition. The vulnerability is addressed by a patch included in version 1.3.0.
Potential Impact
Exploitation of this vulnerability can cause the nimiq-blockchain node to panic and crash during history synchronization, resulting in a denial of service. There is no impact on confidentiality or integrity reported. No known exploits are in the wild.
Mitigation Recommendations
Upgrade to nimiq-blockchain version 1.3.0 or later, which includes a patch that removes the unsafe assert and properly validates input before processing. No workarounds are available for affected versions prior to 1.3.0. Patch status is not explicitly stated but the fix is included in version 1.3.0, so upgrading is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-25T16:21:40.867Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e9290319fe3cd2cde955ab
Added to database: 4/22/2026, 8:01:07 PM
Last enriched: 4/22/2026, 8:16:22 PM
Last updated: 4/22/2026, 10:43:29 PM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.