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.
TBD
No know workarounds.
{
"github_reviewed": true,
"cwe_ids": [
"CWE-1284",
"CWE-20"
],
"severity": "CRITICAL",
"nvd_published_at": "2026-04-09T21:16:11Z",
"github_reviewed_at": "2026-04-10T19:55:04Z"
}