CVE-2026-34068— Nimiq 数据伪造问题漏洞

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

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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

密码学签名的验证不恰当

Nimiq 数据伪造问题漏洞

Nimiq是Nimiq开源的一个Albatross协议的Rust实现。 Nimiq 1.3.0之前版本存在数据伪造问题漏洞，该漏洞源于nimiq-transaction中质押合约接受设置new_voting_key=Some(...)但省略new_proof_of_knowledge的UpdateValidator交易。这跳过了在聚合公钥时防止BLS流氓密钥攻击所需的知识证明要求。由于tendermint宏块验证会聚合验证者投票密钥并针对该聚合公钥验证单个聚合BLS签名，验证者集中的流氓密钥投票密钥可能允

N/A

N/A