Skip to content

CVE-2026-34068 nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge

MediumCVSS 6.8 EPSS 0.21%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
crates.io nimiq-transaction(crates.io) <= 0.2.0 after 0.2.0 Fixed
nimiq proof-of-stake < 1.3.0 1.3.0 Fixed
nimiq-transaction = < 1.3.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
nimiq-transaction = < 1.3.0 No fix listed
crates.io nimiq-transaction(crates.io) <= 0.2.0 No fix listed
nimiq proof-of-stake < 1.3.0 1.3.0

References