CVE-2026-34068

The record

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.

Affected packages

Related vulnerabilities

• GHSA-pf4j-pf3w-95f9 nimiq-transaction: UpdateValidator transactions allows voting key change without… Same vulnerability
• CVE-2026-34067 nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust… Also affects nimiq-transaction
• GHSA-264v-m8fm-76jm nimiq-transaction: Panic via `HistoryTreeProof` length mismatch Also affects nimiq-transaction
• CVE-2026-87947 Improper Verification of Cryptographic Signature vulnerability in Drupal SAML SSO… CWE-347
• CVE-2026-84918 Improper Verification of Cryptographic Signature vulnerability in Drupal Monobank payment… CWE-347
• CVE-2026-102271 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102272 PyJWT is a Python implementation of JSON Web Token standards. CWE-347
• CVE-2026-102273 PyJWT is a Python implementation of JSON Web Token standards. CWE-347