CVE-2026-34067: nimiq-transaction Panic Vulnerability

LOW
Advisory Identifier: GHSA-264v-m8fm-76jm
CVSS 3.1
CWE-617
Published
Advisory Summary

CVE-2026-34067 is a LOW (CVSS 3.1) panic vulnerability (CWE-617: Reachable Assertion) affecting nimiq-transaction libraries in the crates.io ecosystem. The issue involves panic via `historytreeproof` length mismatch. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34067 at a Glance

CVE Identifier CVE-2026-34067
GHSA Identifier GHSA-264v-m8fm-76jm
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-617: Reachable Assertion
Affected Product nimiq-transaction
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 3.1

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

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

How to Fix CVE-2026-34067

To remediate this vulnerability, upgrade all affected nimiq-transaction 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-transaction fixed: Latest secure release
Upgrade nimiq-transaction 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-transaction

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34067, inspect your project dependencies for nimiq-transaction:

inspect dependencies for nimiq-transaction

Analyze the terminal output to locate any version of nimiq-transaction 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-transaction, 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 `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. ### Patches [The patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a) is included as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0). ### Workarounds No known workarounds know.

CVE-2026-34067 Affected nimiq-transaction Versions

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

References

Frequently Asked Questions

What is CVE-2026-34067?
CVE-2026-34067 is a security vulnerability in nimiq-transaction involving Panic via `HistoryTreeProof` length mismatch under CWE-617: Reachable Assertion.
Which nimiq-transaction versions are affected?
Affected versions include releases prior to current release patches across affected packages: nimiq-transaction.
What version fixes CVE-2026-34067?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is nimiq-transaction affected?
Yes, nimiq-transaction 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-34067?
CVE-2026-34067 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-34067?
CVE-2026-34067 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-34067?
Run the dependency tree command: 'inspect dependencies for nimiq-transaction'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-264v-m8fm-76jm",
  "modified" : "2026-04-27T16:22:44Z",
  "published" : "2026-04-22T19:20:50Z",
  "aliases" : [ "CVE-2026-34067" ],
  "summary" : "nimiq-transaction: Panic via `HistoryTreeProof` length mismatch",
  "details" : "### Impact\n`HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. \n\nThe proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch.\n\n### Patches\n[The patch for this vulnerability](https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a) is included as part of [v1.3.0](https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0).\n\n### Workarounds\nNo known workarounds know.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "nimiq-transaction"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34067"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/pull/3659"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a"
  }, {
    "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" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-22T19:20:50Z",
    "nvd_published_at" : "2026-04-22T21:17:07Z"
  }
}