CVE-2026-46539: CWE-345: Insufficient Verification of Data Authenticity in nimiq core-rs-albatross
A logic flaw in the Nimiq core-rs-albatross implementation prior to version 1. 4. 0 causes the BlockInclusionProof::is_block_proven function to incorrectly return true without cryptographic verification under specific conditions. This allows an attacker to forge a MacroBlock header at a critical election block position, bypassing hash and signature checks. The issue is fixed in version 1. 4. 0.
AI Analysis
Technical Summary
Nimiq's Rust implementation of the Proof-of-Stake protocol using the Albatross consensus algorithm contains a vulnerability (CVE-2026-46539) in versions before 1.4.0. The BlockInclusionProof::is_block_proven function has a logic flaw where it returns true without performing cryptographic verification if get_interlink_hops returns an empty list. This situation arises when the target block is at the election block position immediately before the election head's epoch. An attacker can exploit this to forge a MacroBlock header for that epoch position, which will be accepted as proven without any hash or signature verification, compromising the integrity of the consensus. The vulnerability has a CVSS 3.1 base score of 5.9 (medium severity) and impacts data integrity but not confidentiality or availability. The issue has been patched in version 1.4.0.
Potential Impact
The vulnerability allows an attacker to forge a MacroBlock header at a specific election block position without cryptographic verification, leading to a loss of data integrity in the blockchain consensus process. There is no impact on confidentiality or availability. This could undermine trust in the blockchain state if exploited.
Mitigation Recommendations
Upgrade to Nimiq core-rs-albatross version 1.4.0 or later, where the vulnerability has been patched. No other mitigation or temporary fix is indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in version 1.4.0.
CVE-2026-46539: CWE-345: Insufficient Verification of Data Authenticity in nimiq core-rs-albatross
Description
A logic flaw in the Nimiq core-rs-albatross implementation prior to version 1. 4. 0 causes the BlockInclusionProof::is_block_proven function to incorrectly return true without cryptographic verification under specific conditions. This allows an attacker to forge a MacroBlock header at a critical election block position, bypassing hash and signature checks. The issue is fixed in version 1. 4. 0.
CVSS v3.1
Score 5.9medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Nimiq's Rust implementation of the Proof-of-Stake protocol using the Albatross consensus algorithm contains a vulnerability (CVE-2026-46539) in versions before 1.4.0. The BlockInclusionProof::is_block_proven function has a logic flaw where it returns true without performing cryptographic verification if get_interlink_hops returns an empty list. This situation arises when the target block is at the election block position immediately before the election head's epoch. An attacker can exploit this to forge a MacroBlock header for that epoch position, which will be accepted as proven without any hash or signature verification, compromising the integrity of the consensus. The vulnerability has a CVSS 3.1 base score of 5.9 (medium severity) and impacts data integrity but not confidentiality or availability. The issue has been patched in version 1.4.0.
Potential Impact
The vulnerability allows an attacker to forge a MacroBlock header at a specific election block position without cryptographic verification, leading to a loss of data integrity in the blockchain consensus process. There is no impact on confidentiality or availability. This could undermine trust in the blockchain state if exploited.
Mitigation Recommendations
Upgrade to Nimiq core-rs-albatross version 1.4.0 or later, where the vulnerability has been patched. No other mitigation or temporary fix is indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in version 1.4.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-14T20:42:31.368Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a28a8098dd33fbd8595f122
Added to database: 6/9/2026, 11:55:53 PM
Last enriched: 6/10/2026, 12:12:15 AM
Last updated: 6/10/2026, 1:38:44 AM
Views: 3
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.