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.
Original description
The description as published by the source.
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.4.0, a denial-of-service vulnerability exists in the Ed25519 multisig delinearization code path. Ed25519PublicKey::delinearize() in keys/src/multisig/mod.rs called .unwrap() on curve point decompression, which panics when a public key is constructed from 32 bytes that do not represent a valid point on the Ed25519 curve. Ed25519PublicKey construction only validates byte length, not curve membership, so invalid keys can reach the delinearization path and crash the hosting process. This issue has been patched in version 1.4.0.
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-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.
A vulnerability (CWE-617) exists in nimiq-keys. Attackers reach the vulnerable code path via Ed25519PublicKey without authentication.
Check the vendor advisory for the affected versions of nimiq-keys. Attack surface: Ed25519PublicKey.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.4.0.
Workaround: No code-level workaround exists short of the patch.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No code-level workaround exists short of the patch.パッチが適用されるまでの応急処置として、No code-level workaround exists short of the patch. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade nimiq-keys to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com