Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

Quick assessment

Affected
nimiq nimiq-transaction
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

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

CVSS 6.8 · Medium EPSS 0.26% · P17

Possible ATT&CK Techniques 1 AI

T1556 · Modify Authentication Process
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-34068

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
密码学签名的验证不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Nimiq 数据伪造问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Nimiq是Nimiq开源的一个Albatross协议的Rust实现。 Nimiq 1.3.0之前版本存在数据伪造问题漏洞,该漏洞源于nimiq-transaction中质押合约接受设置new_voting_key=Some(...)但省略new_proof_of_knowledge的UpdateValidator交易。这跳过了在聚合公钥时防止BLS流氓密钥攻击所需的知识证明要求。由于tendermint宏块验证会聚合验证者投票密钥并针对该聚合公钥验证单个聚合BLS签名,验证者集中的流氓密钥投票密钥可能允
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
nimiq nimiq-transaction < 1.3.0 -

II. Public POCs for CVE-2026-34068

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-34068

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-34068 (2)

Same Patch Batch · nimiq · 2026-04-22 · 8 CVEs total

CVE-2026-33471 9.6 CRITICAL nimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation
CVE-2026-34063 7.5 HIGH network-libp2p: Peer can crash the node by opening discovery protocol substream twice
CVE-2026-34065 7.5 HIGH nimiq-primitives: Node crash due to missing interlink validation in election macro block p
CVE-2026-34062 5.3 MEDIUM Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/respo
CVE-2026-34064 5.3 MEDIUM nimiq-account: Vesting insufficient funds error can panic
CVE-2026-34066 5.3 MEDIUM nimiq-blockchain: Peer-triggerable panic during history sync
CVE-2026-34067 3.1 LOW nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch

IV. Related Vulnerabilities

V. Comments for CVE-2026-34068

No comments yet


Leave a comment