Advisory

GHSA-j99g-7rqw-q9jg

Also known as: CVE-2026-34066

Summary

nimiq-blockchain: Peer-triggerable panic during history sync

Details

Impact
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.

Patches
The patch for this vulnerability is included as part of v1.3.0.

Workarounds
No known workarounds.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-22 19:23 UTC
Modified
2026-05-05 16:10 UTC

Affected packages and fixes

nimiq-blockchain

crates.io · All systems

Affected

  • introduced 0, last affected 0.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences