CVE-2026-40093
Nimiq Proof-Of-Stake ≤ 1.3.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-40093 is a high-severity Improper Validation of Specified Quantity in Input (CWE-1284) vulnerability in Nimiq Nimiq Proof-Of-Stake. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-40093 is a vulnerability in the nimiq-blockchain component, which provides persistent block storage for Nimiq's Rust implementation. Affecting versions 1.3.0 and earlier, the issue stems from incomplete block timestamp validation. While the code enforces that non-skip blocks have a timestamp greater than or equal to the parent block's timestamp and skip blocks have a timestamp exactly equal to the parent timestamp plus MIN_PRODUCER_TIMEOUT, there is no upper bound check against the wall clock.
A malicious block-producing validator can exploit this vulnerability over the network with low privileges. By setting block timestamps arbitrarily far in the future, the attacker directly manipulates reward calculations through Policy::supply_at() and batch_delay() functions in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule. The CVSS v3.1 base score is 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H), linked to CWE-1284 (Improvable Triple-DES Key Sizes).
Mitigation details are available in the GitHub security advisory at https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-49xc-52mp-cc9j.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21146
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.7.2V1.4.2V2.1.1V2.2.1
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping acceptance of malformed quantities before they can be used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper quantity/length validation in input handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing quantity validation but does not itself implement the control.
Secure development lifecycle mandates input validation for quantity fields, directly preventing CWE-1284.
Application security requirements explicitly call for validation of size/length inputs, mitigating CWE-1284.
Secure architecture principles encourage robust input handling but do not specifically address quantity validation.
Secure coding standards require explicit checks on numeric quantity inputs, fully addressing CWE-1284.