CVE-2026-35468
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk41th percentile - higher than 41% of all known CVEs
Summary
In the Nimiq Proof-of-Stake Rust implementation (core-rs-albatross), two consensus request handlers assume the history index is always available, causing a panic (unwrap) during node sync. A remote attacker can crash the node.
Risk Assessment
An attacker can crash a full node during synchronization, leading to network disruption.
Recommendation
Update core-rs-albatross to version 1.3.0 or later.
Original NVD description (English source)
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.