CVE-2026-34067 | nimiq core-rs-albatross up to 1.2.x HistoryTreeProof::verify assertion

VDB-359057 · CVE-2026-34067 · GCVE-0-2026-34067 NIMIQ CORE-RS-ALBATROSS UP TO 1.2.X HISTORYTREEPROOF::VERIFY ASSERTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 3.0 $0-$5k 2.50+ Summaryinfo A vulnerability classified as problematic has been found in nimiq core-rs-albatross up to 1.2.x. The affected element is the function HistoryTreeProof::verify. The manipulation leads to assertion. This vulnerability is uniquely identified as CVE-2026-34067. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in nimiq core-rs-albatross up to 1.2.x. This issue affects the function HistoryTreeProof::verify. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. 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. Impacted is availability. The summary by CVE is: 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. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-34067 since 03/25/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. Upgrading to version 1.3.0 eliminates this vulnerability. Productinfo Vendor nimiq Name core-rs-albatross Version 1.0 1.1 1.2 Website Product: https://github.com/nimiq/core-rs-albatross/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 3.1 VulDB Meta Temp Score: 3.0 VulDB Base Score: 3.1 VulDB Temp Score: 3.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 3.1 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Assertion CWE: CWE-617 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: core-rs-albatross 1.3.0 Timelineinfo 03/25/2026 CVE reserved 04/22/2026 +27 days Advisory disclosed 04/22/2026 +0 days VulDB entry created 04/22/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-34067 (🔒) GCVE (CVE): GCVE-0-2026-34067 GCVE (VulDB): GCVE-100-359057 Entryinfo Created: 04/22/2026 22:30 Changes: 04/22/2026 22:30 (63) Complete: 🔍 Cache ID: 99:738:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸