nimiq-blockchain: Validity store off by one error (CVE-2026-46369)
A vulnerability in the Nimiq blockchain Rust implementation (up to version 1.5.0) causes a validity store off-by-one error that allows replaying signed transactions within a specific block window, resulting in double updates to sender and recipient balances. This flaw is fixed in version 1.5.1.
AI Analysis
Technical Summary
Nimiq blockchain versions prior to 1.5.1 contain a validity store off-by-one error due to a strict lower-bound comparison that prematurely expires stored transactions relative to Transaction::is_valid_at. This allows a remote attacker to replay the same signed transaction during a window of blocks_per_batch minus one blocks, causing the sender and recipient balances to be updated twice. The issue is addressed in version 1.5.1.
Potential Impact
An attacker can replay a signed transaction within a limited block window, causing double updates to account balances (sender and recipient). This impacts the integrity of transaction processing but does not affect confidentiality or availability.
Mitigation Recommendations
Upgrade to Nimiq blockchain version 1.5.1 or later, where the validity store off-by-one error is fixed. Since a patch is available, applying this official fix is the recommended remediation.
nimiq-blockchain: Validity store off by one error (CVE-2026-46369)
Description
A vulnerability in the Nimiq blockchain Rust implementation (up to version 1.5.0) causes a validity store off-by-one error that allows replaying signed transactions within a specific block window, resulting in double updates to sender and recipient balances. This flaw is fixed in version 1.5.1.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Nimiq blockchain versions prior to 1.5.1 contain a validity store off-by-one error due to a strict lower-bound comparison that prematurely expires stored transactions relative to Transaction::is_valid_at. This allows a remote attacker to replay the same signed transaction during a window of blocks_per_batch minus one blocks, causing the sender and recipient balances to be updated twice. The issue is addressed in version 1.5.1.
Potential Impact
An attacker can replay a signed transaction within a limited block window, causing double updates to account balances (sender and recipient). This impacts the integrity of transaction processing but does not affect confidentiality or availability.
Mitigation Recommendations
Upgrade to Nimiq blockchain version 1.5.1 or later, where the validity store off-by-one error is fixed. Since a patch is available, applying this official fix is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3763-qp59-59vf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-46369"]
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a7c9b2dbf8831d539cdb66f
Added to database: 08/12/2026, 16:11:25 UTC
Last enriched: 09/12/2026, 05:33:16 UTC
Last updated: 09/26/2026, 12:03:07 UTC
Views: 52
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.