nimiq-blockchain
Affected
- introduced
0, fixed1.5.1(semver)
Fixed versions
1.5.1
Fix
- Fixed version
1.5.1cargo update -p nimiq-blockchain --precise 1.5.1
Advisory
Also known as: CVE-2026-46369
nimiq-blockchain: Validity store off by one error
Impact
The validity store treats a transaction with stored block_number = X as "in window" only when X > last_bn - transaction_validity_window_blocks (strict inequality). However the protocol's Transaction::is_valid_at accepts a transaction for inclusion in any block in [validity_start_height - blocks_per_batch, validity_start_height + window - 1]. By choosing validity_start_height = X + blocks_per_batch (the largest value still compatible with first inclusion at block X), an attacker can replay the same signed transaction in any block B such that X + window < B < validity_start_height + window, i.e., a contiguous window of blocks_per_batch - 1 blocks (59 on MainNet, ~10 minutes) during which the replay-protection check fails to flag it. The same transaction is then executed twice: the sender is debited twice, the recipient credited twice.
Patches
https://github.com/nimiq/core-rs-albatross/pull/3772
Workarounds
No known workarounds
High Basis: The source's own band: HIGH
0, fixed 1.5.1 (semver)1.5.1
1.5.1cargo update -p nimiq-blockchain --precise 1.5.1Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0