Vulnerability in nimiq-blockchain (CVE-2026-46543)
Summary
Vulnerability in nimiq-blockchain (CVE-2026-46543). Risk of unauthorized operations or information disclosure. Exploitable via get_epoch_chunks. Mitigation: upgrade to 1.5.0 or later.
Original description
The description as published by the source.
Impact
A remote peer can crash any full node by sending a RequestBatchSet message containing the genesis block's hash. The handler calls get_epoch_chunks which iterates backwards through macro blocks using Policy::macro_block_before. When it reaches the genesis block number, macro_block_before panics with "No macro blocks before genesis block".
Patches
The patch for this vulnerability is formally released as part of v1.5.0.
Workarounds
No Workaround, although requesting the genesis batch set is not used during normal operation.
Resources
See PR.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46543 has been found in nimiq-blockchain.
Attackers can target a specific entry point like get_epoch_chunks over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade nimiq-blockchain to 1.5.0 or later.
If unsure, ask your IT team or search "nimiq-blockchain CVE-2026-46543" on the vendor's site.
CVE-2026-46543 (nimiq-blockchain) — CWE-617 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: get_epoch_chunks / macro_block_before
Patched: 1.5.0 — apply immediately
Workaround: No Workaround, although requesting the genesis batch set is not used during normal operation.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-617) exists in nimiq-blockchain. Attackers reach the vulnerable code path via get_epoch_chunks without authentication.
Check the vendor advisory for the affected versions of nimiq-blockchain. Attack surface: get_epoch_chunks / macro_block_before.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.5.0.
Workaround: No Workaround, although requesting the genesis batch set is not used during normal operation.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nimiq-blockchain' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nimiq-blockchain' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nimiq-blockchainを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No Workaround, although requesting the genesis batch set is not used during normal operation.パッチが適用されるまでの応急処置として、No Workaround, although requesting the genesis batch set is not used during normal operation. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade nimiq-blockchain to 1.5.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com
- web security-advisories@github.com
- web github.com