CVEvulnerability

CVE-2026-34066

5.3 MEDIUM Published 2026-04-22 Modified 2026-10-26 Official page ↗
Status
Analyzed
Published
2026-04-22
Last modified
2026-10-26
Assigner
[email protected]
CVSS 3.1 ([email protected])
5.3 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
Weaknesses
CWE-20, CWE-617, CWE-754

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.

Affected configurations

• nimiq nimiq proof-of-stake (< 1.3.0)

Related

Weakness · CWE (3)

  • CWE-20 Improper Input Validation weakness
  • CWE-617 Reachable Assertion weakness
  • CWE-754 Improper Check for Unusual or Exceptional Conditions weakness

References