CVE-2026-40093: nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation

Q: How do I fix CVE-2026-40093?

nimiq proof-of-stake: upgrade to 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-40093 being exploited?

CVE-2026-40093 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-40093 affect?

CVE-2026-40093 affects nimiq proof-of-stake. Severity is high (CVSS 8.1). 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_PRO

Routine

HIGH 8.1UPGRADE

CVE-2026-40093 is a high-severity flaw (CVSS 8.1) affecting nimiq proof-of-stake. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 affec

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-1284
Published	2026-04-09
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: nimiq

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-09 21:16 UTCPublished CVE record published
2026-10-26 00:10 UTCUpdated Record last modified

nimiq nimiq proof-of-stake UPGRADE

Affected: < 1.3.0

Fixed in: 1.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy nimiq-proof-of-stake || rpm -q nimiq-proof-of-stake || nimiq-proof-of-stake --version

2. UPGRADE to 1.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nimiq-proof-of-stake

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nimiq-proof-of-stake

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40093?

nimiq proof-of-stake: upgrade to 1.3.0. Exact commands for each OS are on this page.

Is CVE-2026-40093 being exploited?

CVE-2026-40093 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40093 affect?

CVE-2026-40093 affects nimiq proof-of-stake. Severity is high (CVSS 8.1). 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_PRO

How urgent is CVE-2026-40093?

Priority 34/100. High severity

References

← Back to latest CVEs