Loading vulnerability…
CVE-2026-40093 affects nimiq-blockchain, the persistent block storage component for Nimiq's Rust implementation. In version 1.3.0 and earlier, block timestamp validation only enforces relative consistency with the parent block: non-skip blocks must satisfy timestamp >= parent.timestamp, and skip blocks must satisfy timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT. Based on the provided content, there is no visible upper-bound validation against the wall clock. As a result, a malicious block-producing validator can create blocks with timestamps arbitrarily far in the future. This timestamp manipulation directly influences reward logic in Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, allowing the monetary supply to be calculated as if more time had elapsed than actually had, thereby inflating issuance beyond the intended emission schedule.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.