CVE-2026-34066CWE-20CWE-617CWE-754

nimiq-blockchain: Peer-triggerable panic during history sync

Medium · published April 22, 2026

CVSS v3.1
5.3
EPSS
0%
Percentile
33.2
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.3 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00401 · 33.2th percentile
Weaknesses
CWE-20 · Improper Input Validation; CWE-617 · Reachable Assertion; CWE-754 · Improper Check for Unusual or Exceptional Conditions
Published
2026-04-22T19:47Z
EPSS history
Timeline
  • 22 APR 19:47Z
    nimiq-blockchain: Peer-triggerable panic during history sync
    cvelistv5