CVE-2026-34061: CWE-345: Insufficient Verification of Data Authenticity in nimiq core-rs-albatross
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, an elected validator proposer can send an election macro block whose header.interlink does not match the canonical next interlink. Honest validators accept that proposal in verify_macro_block_proposal() because the proposal path validates header shape, successor relation, proposer, body root, and state, but never checks the interlink binding for election blocks. The same finalized block is later rejected by verify_block() during push with InvalidInterlink. Because validators prevote and precommit the malformed header hash itself, the failure happens after Tendermint decides the block, not before voting. This issue has been patched in version 1.3.0.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-34061) in the Rust implementation of the Nimiq Proof-of-Stake protocol (core-rs-albatross) involves insufficient verification of data authenticity (CWE-345) related to election macro block headers. Specifically, prior to version 1.3.0, the verify_macro_block_proposal() function does not validate that the header.interlink matches the canonical next interlink, allowing a proposer to submit a malformed block header. Although the malformed block is accepted initially, it is later rejected by verify_block() during block push due to an InvalidInterlink error. This failure occurs after Tendermint consensus has finalized the block, which can cause issues in block processing and availability. The vulnerability has been patched in version 1.3.0.
Potential Impact
This vulnerability can cause finalized blocks to be rejected after consensus, leading to potential disruption in block processing and availability of the blockchain network. There is no direct impact on confidentiality or integrity of data, but the availability of the network may be affected due to the delayed detection of malformed blocks. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to nimiq/core-rs-albatross version 1.3.0 or later, where this vulnerability has been patched. Since the vendor advisory indicates the issue is fixed in version 1.3.0, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.
CVE-2026-34061: CWE-345: Insufficient Verification of Data Authenticity in nimiq core-rs-albatross
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, an elected validator proposer can send an election macro block whose header.interlink does not match the canonical next interlink. Honest validators accept that proposal in verify_macro_block_proposal() because the proposal path validates header shape, successor relation, proposer, body root, and state, but never checks the interlink binding for election blocks. The same finalized block is later rejected by verify_block() during push with InvalidInterlink. Because validators prevote and precommit the malformed header hash itself, the failure happens after Tendermint decides the block, not before voting. This issue has been patched in version 1.3.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-34061) in the Rust implementation of the Nimiq Proof-of-Stake protocol (core-rs-albatross) involves insufficient verification of data authenticity (CWE-345) related to election macro block headers. Specifically, prior to version 1.3.0, the verify_macro_block_proposal() function does not validate that the header.interlink matches the canonical next interlink, allowing a proposer to submit a malformed block header. Although the malformed block is accepted initially, it is later rejected by verify_block() during block push due to an InvalidInterlink error. This failure occurs after Tendermint consensus has finalized the block, which can cause issues in block processing and availability. The vulnerability has been patched in version 1.3.0.
Potential Impact
This vulnerability can cause finalized blocks to be rejected after consensus, leading to potential disruption in block processing and availability of the blockchain network. There is no direct impact on confidentiality or integrity of data, but the availability of the network may be affected due to the delayed detection of malformed blocks. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to nimiq/core-rs-albatross version 1.3.0 or later, where this vulnerability has been patched. Since the vendor advisory indicates the issue is fixed in version 1.3.0, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-25T16:21:40.866Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d03f860a160ebd92619e1b
Added to database: 4/3/2026, 10:30:30 PM
Last enriched: 4/11/2026, 9:24:02 AM
Last updated: 5/20/2026, 8:52:25 PM
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.