CVE-2026-40093: CWE-1284: Improper Validation of Specified Quantity in Input in nimiq core-rs-albatross
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp >= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.
AI Analysis
Technical Summary
The vulnerability exists in the nimiq-blockchain Rust implementation, specifically in the block timestamp validation logic. While the code enforces that timestamps for non-skip blocks are greater than or equal to the parent block's timestamp and that skip blocks have timestamps exactly equal to the parent's timestamp plus a minimum producer timeout, it does not enforce an upper bound relative to the actual wall clock time. This flaw enables a malicious validator to assign future timestamps to blocks, which manipulates reward calculations in the Policy::supply_at() and batch_delay() functions, resulting in an unintended inflation of the blockchain's monetary supply.
Potential Impact
The impact is a high-severity inflation of the blockchain's monetary supply due to manipulated block timestamps. This compromises the integrity of the emission schedule and could undermine economic trust in the Nimiq blockchain. There is no direct confidentiality or availability impact reported. No known exploits in the wild have been identified at this time.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or vendor advisory is currently available. Users should monitor the vendor's advisory channels for updates and apply any forthcoming patches promptly. Until a fix is released, restricting block-producing validators to trusted parties and monitoring for anomalous block timestamps could help mitigate risk.
CVE-2026-40093: CWE-1284: Improper Validation of Specified Quantity in Input in nimiq core-rs-albatross
Description
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp >= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in the nimiq-blockchain Rust implementation, specifically in the block timestamp validation logic. While the code enforces that timestamps for non-skip blocks are greater than or equal to the parent block's timestamp and that skip blocks have timestamps exactly equal to the parent's timestamp plus a minimum producer timeout, it does not enforce an upper bound relative to the actual wall clock time. This flaw enables a malicious validator to assign future timestamps to blocks, which manipulates reward calculations in the Policy::supply_at() and batch_delay() functions, resulting in an unintended inflation of the blockchain's monetary supply.
Potential Impact
The impact is a high-severity inflation of the blockchain's monetary supply due to manipulated block timestamps. This compromises the integrity of the emission schedule and could undermine economic trust in the Nimiq blockchain. There is no direct confidentiality or availability impact reported. No known exploits in the wild have been identified at this time.
Mitigation Recommendations
Patch status is not yet confirmed — no official fix or vendor advisory is currently available. Users should monitor the vendor's advisory channels for updates and apply any forthcoming patches promptly. Until a fix is released, restricting block-producing validators to trusted parties and monitoring for anomalous block timestamps could help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-09T01:41:38.535Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d814ae1cc7ad14da21652c
Added to database: 4/9/2026, 9:05:50 PM
Last enriched: 4/17/2026, 12:02:07 PM
Last updated: 5/25/2026, 12:22:36 PM
Views: 64
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.
External Links
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.