{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "cpe": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
            "extracted_events": [
              {
                "introduced": "0"
              },
              {
                "fixed": "1.3.0"
              }
            ],
            "source": [
              "CPE_RANGE",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5bd15d9af710abeecdfb63d0a721dc883efb59c4"
            },
            {
              "fixed": "6ff0800e8e031363e787c827d8d033e5694e4e6a"
            }
          ],
          "repo": "https://github.com/nimiq/core-rs-albatross",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-264v-m8fm-76jm"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-617"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34067.json"
  },
  "details": "nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `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. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.",
  "id": "CVE-2026-34067",
  "modified": "2026-07-08T05:39:11.549376240Z",
  "published": "2026-04-22T19:52:43.916Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34067.json"
    },
    {
      "type": "ADVISORY",
      "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": "FIX",
      "url": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a"
    },
    {
      "type": "FIX",
      "url": "https://github.com/nimiq/core-rs-albatross/pull/3659"
    }
  ],
  "schema_version": "1.7.5",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch"
}