← Back
CVE-2026-46542
medium
CVSS 4.3
Vulnerability in nimiq-keys (CVE-2026-46542)
Summary
vulnerability in nimiq-keys (CVE-2026-46542). Risk of unauthorized operations or information disclosure. Exploitable via ``Ed25519PublicKey``. Mitigation: upgrade to `1.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46542** has been found in nimiq-keys.
Attackers can target a specific entry point like ``Ed25519PublicKey`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade nimiq-keys to **1.4.0** or later.
If unsure, ask your IT team or search "nimiq-keys CVE-2026-46542" on the vendor's site.
CVE-2026-46542 (nimiq-keys) — CWE-617 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Ed25519PublicKey`
Patched: `1.4.0` — apply immediately
Workaround: No code-level workaround exists short of the patch.
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-617) exists in nimiq-keys. Attackers reach the vulnerable code path via ``Ed25519PublicKey`` without authentication.
📍 Affected scope
nimiq-keys — . Attack surface: `Ed25519PublicKey`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.4.0**.
🛡️ Workaround
Workaround: No code-level workaround exists short of the patch.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'nimiq-keys' .` 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-keys' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nimiq-keys` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
No code-level workaround exists short of the patch.パッチが適用されるまでの応急処置として、No code-level workaround exists short of the patch. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade nimiq-keys to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
nimiq-keys
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.0"}]}]
crates.io
nimiq-keys
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.4.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-46542
- package https://github.com/nimiq/core-rs-albatross
- web https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-h9cc-w26m-j342
- web https://github.com/nimiq/core-rs-albatross/pull/3713
- web https://github.com/nimiq/core-rs-albatross/commit/3bc449a8138960c4de6bfd506bad1730c621d4de
- web https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0
- web https://github.com/advisories/GHSA-h9cc-w26m-j342