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
nimiq-blockchain's Rust implementation (core-rs-albatross) versions up to 1.3.0 validate block timestamps to ensure they are not earlier than the parent block's timestamp and enforce specific timing for skip blocks. However, there is no upper bound validation against the current wall clock time. This allows a malicious validator to create blocks with timestamps set arbitrarily far into the future. This timestamp manipulation impacts reward calculation functions (Policy::supply_at() and batch_delay()), causing inflation of the monetary supply beyond the intended emission schedule. The vulnerability is classified as CWE-1284 (Improper Validation of Specified Quantity in Input).
Potential Impact
The vulnerability allows an attacker controlling a block-producing validator to inflate the blockchain's monetary supply by setting future block timestamps without restriction. This undermines the integrity of the reward emission schedule, potentially causing economic damage to the Nimiq blockchain ecosystem. There is no direct confidentiality or availability impact reported. No known exploits are currently observed in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is currently available, users should monitor vendor communications for updates. Until a fix is released, consider restricting block-producing validator permissions or implementing external monitoring for anomalous block timestamps if feasible.
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
nimiq-blockchain's Rust implementation (core-rs-albatross) versions up to 1.3.0 validate block timestamps to ensure they are not earlier than the parent block's timestamp and enforce specific timing for skip blocks. However, there is no upper bound validation against the current wall clock time. This allows a malicious validator to create blocks with timestamps set arbitrarily far into the future. This timestamp manipulation impacts reward calculation functions (Policy::supply_at() and batch_delay()), causing inflation of the monetary supply beyond the intended emission schedule. The vulnerability is classified as CWE-1284 (Improper Validation of Specified Quantity in Input).
Potential Impact
The vulnerability allows an attacker controlling a block-producing validator to inflate the blockchain's monetary supply by setting future block timestamps without restriction. This undermines the integrity of the reward emission schedule, potentially causing economic damage to the Nimiq blockchain ecosystem. There is no direct confidentiality or availability impact reported. No known exploits are currently observed in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is currently available, users should monitor vendor communications for updates. Until a fix is released, consider restricting block-producing validator permissions or implementing external monitoring for anomalous block timestamps if feasible.
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/9/2026, 9:21:12 PM
Last updated: 4/10/2026, 8:14:59 AM
Views: 7
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.