CVE-2026-34069: Nimiq consensus Nimiq-consensus Panics Vulnerability

MODERATE
Advisory Identifier: GHSA-48m6-486p-9j8p
Share
CVSS 5.3
CWE-617
Published
Advisory Summary

CVE-2026-34069 is a MODERATE (CVSS 5.3) nimiq-consensus panics vulnerability (CWE-617: Reachable Assertion) affecting Nimiq consensus libraries in the crates.io ecosystem. The issue involves nimiq-consensus panics via requestmacrochain micro-block locator. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34069 at a Glance

CVE Identifier CVE-2026-34069
GHSA Identifier GHSA-48m6-486p-9j8p
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-617: Reachable Assertion
Affected Product Nimiq consensus
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-34069

To remediate this vulnerability, upgrade all affected Nimiq consensus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nimiq-consensus fixed: Latest secure release 
Upgrade nimiq-consensus to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for nimiq-consensus

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34069, inspect your project dependencies for Nimiq consensus:

inspect dependencies for nimiq-consensus

Analyze the terminal output to locate any version of Nimiq consensus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-617: Reachable Assertion, where the product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. In Nimiq consensus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact An unauthenticated p2p peer can cause the `RequestMacroChain` message handler task to panic by sending a `RequestMacroChain` message where the first locator hash that is on the victim’s main chain is a micro block hash (not a macro block hash). In `RequestMacroChain::handle`, the handler selects the locator based only on "is on main chain", then calls `get_macro_blocks()` and panics via `.unwrap()` when the selected hash is not a macro block (`BlockchainError::BlockIsNotMacro`). ### Patches The patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/pull/3660) is formally released as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0). ### Workarounds No known workarounds.

CVE-2026-34069 Affected Nimiq consensus Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
nimiq-consensus
 crates.io
≤ 1.2.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p
NVD — CVE-2026-34069 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-34069
Nimiq consensus Source Repository REPOSITORY
https://github.com/nimiq/core-rs-albatross/pull/3660
Security Fix Commit FIX COMMIT
https://github.com/nimiq/core-rs-albatross/commit/ae6c1e92342e72f80fd12accbe66ee80dd6802ac
Nimiq consensus Source Repository REPOSITORY
https://github.com/nimiq/core-rs-albatross
Nimiq consensus Release RELEASE
https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0

Frequently Asked Questions

What is CVE-2026-34069?
CVE-2026-34069 is a security vulnerability in Nimiq consensus involving nimiq-consensus panics via RequestMacroChain micro-block locator under CWE-617: Reachable Assertion.
Which Nimiq consensus versions are affected?
Affected versions include releases prior to current release patches across affected packages: nimiq-consensus.
What version fixes CVE-2026-34069?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is nimiq-consensus affected?
Yes, nimiq-consensus is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-34069?
CVE-2026-34069 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-34069?
CVE-2026-34069 is classified under CWE-617: Reachable Assertion (The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.).
How can I check crates.io dependencies for CVE-2026-34069?
Run the dependency tree command: 'inspect dependencies for nimiq-consensus'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-48m6-486p-9j8p",
  "modified" : "2026-04-15T20:56:41Z",
  "published" : "2026-04-13T16:36:00Z",
  "aliases" : [ "CVE-2026-34069" ],
  "summary" : "nimiq-consensus panics via RequestMacroChain micro-block locator",
  "details" : "### Impact\n An unauthenticated p2p peer can cause the `RequestMacroChain` message handler task to panic by sending a `RequestMacroChain` message where the first locator hash that is on the victim’s main chain is a micro block hash (not a macro block hash).\n\nIn `RequestMacroChain::handle`, the handler selects the locator based only on \"is on main chain\", then calls `get_macro_blocks()` and panics via `.unwrap()` when the selected hash is not a macro block (`BlockchainError::BlockIsNotMacro`).\n\n### Patches\nThe patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/pull/3660) is formally released as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0).\n\n### Workarounds\nNo known workarounds.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "nimiq-consensus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.2.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34069"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/pull/3660"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/commit/ae6c1e92342e72f80fd12accbe66ee80dd6802ac"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nimiq/core-rs-albatross"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-617" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-13T16:36:00Z",
    "nvd_published_at" : "2026-04-14T00:16:07Z"
  }
}