CVE-2026-34068 | nimiq core-rs-albatross up to 1.2.x signature verification

VDB-359058 · CVE-2026-34068 · GCVE-0-2026-34068 NIMIQ CORE-RS-ALBATROSS UP TO 1.2.X SIGNATURE VERIFICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.2 $0-$5k 2.25+ Summaryinfo A vulnerability classified as problematic was found in nimiq core-rs-albatross up to 1.2.x. The impacted element is an unknown function. The manipulation results in signature verification. This vulnerability was named CVE-2026-34068. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as problematic, was found in nimiq core-rs-albatross up to 1.2.x. Affected is an unknown function. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on integrity. CVE summarizes: nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available. The advisory is available at github.com. This vulnerability is traded as CVE-2026-34068 since 03/25/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not 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: 5.2 VulDB Meta Temp Score: 5.2 VulDB Base Score: 3.7 VulDB Temp Score: 3.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.8 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: Signature verification CWE: CWE-347 / CWE-345 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-34068 (🔒) GCVE (CVE): GCVE-0-2026-34068 GCVE (VulDB): GCVE-100-359058 Entryinfo Created: 04/22/2026 22:31 Changes: 04/22/2026 22:31 (62) Complete: 🔍 Cache ID: 99:57F:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸