Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nimiq | Nimiq Proof-Of-Stake | <= 1.2.2 |
Related Weaknesses (CWE)
References
- https://github.com/nimiq/core-rs-albatross/commit/0e5c90a6c75b722f3d6091769776a4Patch
- https://github.com/nimiq/core-rs-albatross/pull/3667Patch
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0Release Notes
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wVendor Advisory
FAQ
What is CVE-2026-35468?
CVE-2026-35468 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 ass...
How severe is CVE-2026-35468?
CVE-2026-35468 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-35468?
Check the references section above for vendor advisories and patch information. Affected products include: Nimiq Nimiq Proof-Of-Stake.