← Back
CVE-2026-54541
Vulnerability in nimiq-primitives (CVE-2026-54541)
Summary
vulnerability in nimiq-primitives (CVE-2026-54541). Risk of unauthorized operations or information disclosure. Exploitable via ``TrieChunk``. Mitigation: upgrade to `1.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54541** has been found in nimiq-primitives.
Attackers can target a specific entry point like ``TrieChunk`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade nimiq-primitives to **1.6.0** or later.
If unsure, ask your IT team or search "nimiq-primitives CVE-2026-54541" on the vendor's site.
CVE-2026-54541 (nimiq-primitives) — CWE-248 /
Attack surface: `TrieChunk` / `TrieProofNode` / `is_prefix_of` / `true`
Patched: `1.6.0` — apply immediately
Workaround: None other than syncing only from trusted peers.
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.
❓ What is the problem
**A vulnerability** (CWE-248) exists in nimiq-primitives. Attackers reach the vulnerable code path via ``TrieChunk`` without authentication.
📍 Affected scope
nimiq-primitives — . Attack surface: `TrieChunk` / `TrieProofNode` / `is_prefix_of` / `true`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.6.0**.
🛡️ Workaround
Workaround: None other than syncing only from trusted peers.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'nimiq-primitives' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nimiq-primitives' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nimiq-primitives` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
None other than syncing only from trusted peers.パッチが適用されるまでの応急処置として、None other than syncing only from trusted peers. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade nimiq-primitives to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
nimiq-primitives
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.0"}]}]
References
- web https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-46wq-28cx-mhw4
- web https://github.com/nimiq/core-rs-albatross/pull/3789
- web https://github.com/nimiq/core-rs-albatross/commit/41d35acee1b5cf3bc34ec3ddc1abbc03604e791e
- web https://github.com/nimiq/core-rs-albatross/releases/tag/v1.6.0
- web https://github.com/advisories/GHSA-46wq-28cx-mhw4