LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28402: nimiq/core-rs-albatross's nimiq-blockchain missing proposal body root verification

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28402 can let a malicious or compromised Nimiq validator propose malformed macro blocks that crash validator nodes. The issue affects only validator nodes running nimiq/core-rs-albatross before 1.2.2. Business urgency is highest for organizations operating Nimiq validators, because availability of validation infrastructure may be disrupted.

Executive priority

Treat as high priority only where your organization operates Nimiq validators. The main risk is validator availability disruption, not broad enterprise compromise. Upgrade affected validators promptly to v1.2.2 or later.

Technical view

Before v1.2.2, macro proposal verification checked the header but did not verify that header.body_root matched the macro body hash. Later code assumes that binding and may panic when it is false. The GitHub advisory rates this high, with network access, low complexity, low privileges, no user interaction, limited integrity impact, and high availability impact.

Likely exposure

Exposure appears limited to Nimiq validator nodes using nimiq/core-rs-albatross versions earlier than 1.2.2. Non-validator nodes are explicitly described as not impacted in the provided advisory text.

Exploitation context

A malicious or compromised validator elected as proposer can trigger the condition by publishing a macro block proposal with a mismatched body root. The source bundle does not indicate public exploitation, and this CVE is not marked in KEV.

Researcher notes

The fix adds body root verification to proposal checks. The advisory states no known workarounds. Evidence provided does not support claims of active exploitation or impact beyond validator nodes.

Mitigation direction

  • Upgrade nimiq/core-rs-albatross validator deployments to v1.2.2 or later.
  • Prioritize validators and any infrastructure automatically restarting crashed validator processes.
  • If upgrade timing is constrained, check official Nimiq guidance; no workaround is listed.

Validation and detection

  • Inventory Nimiq validator nodes and record deployed core-rs-albatross versions.
  • Confirm validator nodes are running v1.2.2 or later.
  • Review crash or panic logs around macro block proposal handling.
  • Monitor Nimiq advisory and release pages for follow-up guidance.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-354: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28402 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-28402Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nimiqcore-rs-albatross< 1.2.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-354 · source CWE mapping

Improper Validation of Integrity Check Value

Improper Validation of Integrity Check Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.