What’s Vulnerable › Vulnerabilities

CVE-2026-35468: nimiq/core-rs-albatross: Panic in history index request handlers when a full node runs without the history index

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-04-03 · updated 2026-07-24
• Weakness: CWE-252

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Affected products

• nimiq-transaction: through 1.2.2

References

• https://github.com/nimiq/core-rs-albatross/commit/0e5c90a6c75b722f3d6091769776a4040e694dba
• https://github.com/nimiq/core-rs-albatross/pull/3667
• https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
• https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9

Get alerted when CVE-2026-35468 or the next vulnerability affects your stack