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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-34066— nimiq-blockchain: Peer-triggerable panic during history sync

CVSS 5.3 · Medium EPSS 0.12% · P30
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-34066

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-blockchain: Peer-triggerable panic during history sync
Source: NVD (National Vulnerability Database)
Vulnerability Description
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: &[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
Source: NVD (National Vulnerability Database)
Vulnerability Type
输入验证不恰当
Source: NVD (National Vulnerability Database)
Vulnerability Title
Nimiq 输入验证错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Nimiq是Nimiq开源的一个Albatross协议的Rust实现。 Nimiq 1.3.0之前版本存在输入验证错误漏洞,该漏洞源于nimiq-blockchain中HistoryStore::put_historic_txns使用assert!来强制执行关于HistoricTransaction.block_number的不变量。在历史同步期间,对等方可以影响传递给Blockchain::push_history_sync的history输入,格式错误的历史列表可能违反这些不变量并触发panic。ex
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

VendorProductAffected VersionsCPESubscribe
nimiqnimiq-blockchain < 1.3.0 -

II. Public POCs for CVE-2026-34066

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-34066

登录查看更多情报信息。

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

CVE-2026-334719.6 CRITICALnimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation
CVE-2026-340637.5 HIGHnetwork-libp2p: Peer can crash the node by opening discovery protocol substream twice
CVE-2026-340657.5 HIGHnimiq-primitives: Node crash due to missing interlink validation in election macro block p
CVE-2026-340686.8 MEDIUMnimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-
CVE-2026-340625.3 MEDIUMNimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/respo
CVE-2026-340645.3 MEDIUMnimiq-account: Vesting insufficient funds error can panic
CVE-2026-340673.1 LOWnimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch

IV. Related Vulnerabilities

V. Comments for CVE-2026-34066

No comments yet


Leave a comment