# nimiq-keys: Denial of service in Ed25519 multisig delinearization via invalid curve points

Advisory record · `GHSA-h9cc-w26m-j342`

- **Identifiers:** `GHSA-h9cc-w26m-j342` · `CVE-2026-46542`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-617](https://cwe.mitre.org/data/definitions/617.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 21 May 2026
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 May 2026, 19:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nimiq-keys` (crates.io): affected `<1.4.0`; fixed in `1.4.0`

## 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.

Written 8 Nov 2026.

## 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

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`, from 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](https://osv.dev/vulnerability/GHSA-h9cc-w26m-j342)

## Sources

- [GitHub Advisory Database: GHSA-h9cc-w26m-j342](https://github.com/advisories/GHSA-h9cc-w26m-j342)
- [OSV: GHSA-h9cc-w26m-j342](https://osv.dev/vulnerability/GHSA-h9cc-w26m-j342)
- <https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-h9cc-w26m-j342>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-46542>
- <https://github.com/nimiq/core-rs-albatross/pull/3713>
- <https://github.com/nimiq/core-rs-albatross/commit/3bc449a8138960c4de6bfd506bad1730c621d4de>
- <https://github.com/nimiq/core-rs-albatross>
- <https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h9cc-w26m-j342>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h9cc-w26m-j342/>. Everything for agents: <https://agentprime.io/llms.txt>.
