Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The nimiq-keys crate before 1.4.0 can panic in its Ed25519 multisig delinearization code when given a 32-byte public key that is not a valid Ed25519 curve point, and a similar panic exists in Commitment::from for 32-byte input. An attacker must get a user to include a crafted public key in a multisig operation, which can crash the hosting wallet process (denial of service). Upgrade to nimiq-keys 1.4.0 or later. The source lists no workaround beyond only using public keys from trusted sources.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0023, the 14th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:18 UTC First seen by agentprime
- 31 Oct 2026, 15:18 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-h9cc-w26m-j342
- OSV: GHSA-h9cc-w26m-j342
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-h9cc-w26m-j342
- nvd.nist.gov/vuln/detail/CVE-2026-46542
- github.com/nimiq/core-rs-albatross/pull/3713
- github.com/nimiq/core-rs-albatross/commit/3bc449a8138960c4de6bfd506bad1730c621d4de
- github.com/nimiq/core-rs-albatross
- github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0