CVE-2026-28402: CWE-354: Improper Validation of Integrity Check Value 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.2.2, a malicious or compromised validator that is elected as proposer can publish a macro block proposal where `header.body_root` does not match the actual macro body hash. The proposal can pass proposal verification because the macro proposal verification path validates the header but does not validate the binding `body_root == hash(body)`; later code expects this binding and may panic on mismatch, crashing validators. Note that the impact is only for validator nodes. The patch for this vulnerability is formally released as part of v1.2.2. The patch adds the corresponding body root verification in the proposal checks. No known workarounds are available.
AI Analysis
Technical Summary
The vulnerability CVE-2026-28402 affects the nimiq/core-rs-albatross project, a Rust implementation of the Nimiq Proof-of-Stake consensus protocol based on the Albatross algorithm. Prior to version 1.2.2, the system fails to properly validate the integrity check value binding between the macro block proposal header's body_root field and the actual hash of the macro block body. Specifically, a malicious or compromised validator node acting as proposer can craft a macro block proposal where header.body_root does not match the hash of the macro body. The proposal verification process validates the header but omits verifying that body_root equals the hash of the body, allowing the malformed proposal to pass initial checks. However, subsequent code assumes this binding is valid and attempts to use it, which leads to a panic and crashes the validator node. This results in a denial-of-service condition for validator nodes processing the proposal. The vulnerability is classified under CWE-354 (Improper Validation of Integrity Check Value). Exploitation requires the attacker to have validator privileges and be elected proposer but does not require user interaction. The vulnerability has a CVSS v3.1 score of 7.1 (high severity), reflecting its network attack vector, low complexity, required privileges, and high impact on availability. The patch released in version 1.2.2 adds the missing verification step to ensure that the header.body_root matches the actual hash of the macro body during proposal validation, preventing malformed proposals from causing crashes. No known workarounds exist, so upgrading is essential. There are no known exploits in the wild at this time.
Potential Impact
The primary impact of this vulnerability is a denial-of-service condition affecting validator nodes running vulnerable versions of nimiq/core-rs-albatross. By submitting a malformed macro block proposal with an invalid body root hash, a malicious or compromised validator acting as proposer can cause other validators to crash when processing the proposal. This can disrupt consensus operations, reduce network reliability, and potentially delay block finalization. Since the vulnerability affects only validator nodes, end users and non-validator nodes are not directly impacted. However, if multiple validators crash or are forced offline, the overall network security and availability could degrade, increasing the risk of further attacks or network instability. The requirement that the attacker be an elected proposer limits the attack surface but does not eliminate risk, especially in smaller or permissioned validator sets where a compromised validator could be more easily leveraged. The lack of workarounds means that vulnerable nodes remain exposed until patched, increasing operational risk for organizations running validator infrastructure. The impact on confidentiality and integrity is minimal, as the vulnerability does not allow data leakage or unauthorized data modification beyond the malformed proposal itself. The main concern is availability and network resilience.
Mitigation Recommendations
The definitive mitigation is to upgrade all validator nodes running nimiq/core-rs-albatross to version 1.2.2 or later, which includes the patch that enforces proper validation of the body_root field against the macro body hash during proposal verification. Organizations should implement strict version control and update policies to ensure validators are not running vulnerable versions. Additionally, validators should monitor for abnormal crashes or panics that could indicate exploitation attempts. Network-level controls could be considered to restrict validator proposer roles to trusted entities, reducing the risk of malicious proposals. Implementing redundancy and failover mechanisms for validator nodes can help maintain network availability if some nodes crash. Since no workarounds exist, timely patching is critical. Validator operators should also audit their nodes for signs of compromise and ensure private keys and credentials are securely managed to prevent unauthorized proposer role abuse. Finally, participating in community security advisories and updates from the Nimiq project will help stay informed of any emerging threats or fixes.
Affected Countries
Germany, United States, Netherlands, Switzerland, Singapore, Japan, South Korea, United Kingdom, Canada, Australia
CVE-2026-28402: CWE-354: Improper Validation of Integrity Check Value 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.2.2, a malicious or compromised validator that is elected as proposer can publish a macro block proposal where `header.body_root` does not match the actual macro body hash. The proposal can pass proposal verification because the macro proposal verification path validates the header but does not validate the binding `body_root == hash(body)`; later code expects this binding and may panic on mismatch, crashing validators. Note that the impact is only for validator nodes. The patch for this vulnerability is formally released as part of v1.2.2. The patch adds the corresponding body root verification in the proposal checks. No known workarounds are available.
AI-Powered Analysis
Technical Analysis
The vulnerability CVE-2026-28402 affects the nimiq/core-rs-albatross project, a Rust implementation of the Nimiq Proof-of-Stake consensus protocol based on the Albatross algorithm. Prior to version 1.2.2, the system fails to properly validate the integrity check value binding between the macro block proposal header's body_root field and the actual hash of the macro block body. Specifically, a malicious or compromised validator node acting as proposer can craft a macro block proposal where header.body_root does not match the hash of the macro body. The proposal verification process validates the header but omits verifying that body_root equals the hash of the body, allowing the malformed proposal to pass initial checks. However, subsequent code assumes this binding is valid and attempts to use it, which leads to a panic and crashes the validator node. This results in a denial-of-service condition for validator nodes processing the proposal. The vulnerability is classified under CWE-354 (Improper Validation of Integrity Check Value). Exploitation requires the attacker to have validator privileges and be elected proposer but does not require user interaction. The vulnerability has a CVSS v3.1 score of 7.1 (high severity), reflecting its network attack vector, low complexity, required privileges, and high impact on availability. The patch released in version 1.2.2 adds the missing verification step to ensure that the header.body_root matches the actual hash of the macro body during proposal validation, preventing malformed proposals from causing crashes. No known workarounds exist, so upgrading is essential. There are no known exploits in the wild at this time.
Potential Impact
The primary impact of this vulnerability is a denial-of-service condition affecting validator nodes running vulnerable versions of nimiq/core-rs-albatross. By submitting a malformed macro block proposal with an invalid body root hash, a malicious or compromised validator acting as proposer can cause other validators to crash when processing the proposal. This can disrupt consensus operations, reduce network reliability, and potentially delay block finalization. Since the vulnerability affects only validator nodes, end users and non-validator nodes are not directly impacted. However, if multiple validators crash or are forced offline, the overall network security and availability could degrade, increasing the risk of further attacks or network instability. The requirement that the attacker be an elected proposer limits the attack surface but does not eliminate risk, especially in smaller or permissioned validator sets where a compromised validator could be more easily leveraged. The lack of workarounds means that vulnerable nodes remain exposed until patched, increasing operational risk for organizations running validator infrastructure. The impact on confidentiality and integrity is minimal, as the vulnerability does not allow data leakage or unauthorized data modification beyond the malformed proposal itself. The main concern is availability and network resilience.
Mitigation Recommendations
The definitive mitigation is to upgrade all validator nodes running nimiq/core-rs-albatross to version 1.2.2 or later, which includes the patch that enforces proper validation of the body_root field against the macro body hash during proposal verification. Organizations should implement strict version control and update policies to ensure validators are not running vulnerable versions. Additionally, validators should monitor for abnormal crashes or panics that could indicate exploitation attempts. Network-level controls could be considered to restrict validator proposer roles to trusted entities, reducing the risk of malicious proposals. Implementing redundancy and failover mechanisms for validator nodes can help maintain network availability if some nodes crash. Since no workarounds exist, timely patching is critical. Validator operators should also audit their nodes for signs of compromise and ensure private keys and credentials are securely managed to prevent unauthorized proposer role abuse. Finally, participating in community security advisories and updates from the Nimiq project will help stay informed of any emerging threats or fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-27T15:33:57.289Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a20bf332ffcdb8a2748336
Added to database: 2/27/2026, 9:26:11 PM
Last enriched: 2/27/2026, 9:40:28 PM
Last updated: 2/27/2026, 11:36:27 PM
Views: 4
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.
Related Threats
CVE-2026-28426: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statamic cms
HighCVE-2025-11252: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Signum Technology Promotion and Training Inc. windesk.fm
CriticalCVE-2026-2647
UnknownCVE-2026-28425: CWE-94: Improper Control of Generation of Code ('Code Injection') in statamic cms
HighCVE-2026-28424: CWE-862: Missing Authorization in statamic cms
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing 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.