https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 16:05:48 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-326356 EUVD-2026-326356 https://cve.radiocsirt.org/vuln/euvd-2026-326356 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46542 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46542 https://cve.radiocsirt.org/vuln/ghsa-h9cc-w26m-j342 <p><strong>Affected:</strong> crates.io: nimiq-keys</p> <p>### Impact</p> <p>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.</p> <p>A secondary panic existed in `Commitment::From&lt;[u8; 32]&gt;`, which similarly called `.unwrap()` on a failing curve point decompression.</p> <p>**Who is affected:** Browser and desktop wallet users of the web-client WASM library and the `nimiq-wallet` crate, when initiating a multisig operation with an attacker-supplied public key. An attacker must convince the user to include a crafted public key in a multisig setup — this is not a remotely triggerable node/validator crash.</p> <p>**Who is NOT affected:** Validator nodes, consensus, blockchain, mempool, and networking code. There is no on-chain multisig account type; multisig is a purely client-side construct, and no validator/consensus code calls the multisig delinearization path.</p> <p>### Patches</p> <p>See [PR](https://github.com/nimiq/core-rs-albatross/pull/3713).</p> <p>### Workarounds</p> <p>No code-level workaround exists short of the patch. Users of wallet applications can mitigate exposure by only performing multisig operations with public keys received from t…</p> <p><strong>Affected:</strong> crates.io: nimiq-keys</p> <p>### Impact</p> <p>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.</p> <p>A secondary panic existed in `Commitment::From&lt;[u8; 32]&gt;`, which similarly called `.unwrap()` on a failing curve point decompression.</p> <p>**Who is affected:** Browser and desktop wallet users of the web-client WASM library and the `nimiq-wallet` crate, when initiating a multisig operation with an attacker-supplied public key. An attacker must convince the user to include a crafted public key in a multisig setup — this is not a remotely triggerable node/validator crash.</p> <p>**Who is NOT affected:** Validator nodes, consensus, blockchain, mempool, and networking code. There is no on-chain multisig account type; multisig is a purely client-side construct, and no validator/consensus code calls the multisig delinearization path.</p> <p>### Patches</p> <p>See [PR](https://github.com/nimiq/core-rs-albatross/pull/3713).</p> <p>### Workarounds</p> <p>No code-level workaround exists short of the patch. Users of wallet applications can mitigate exposure by only performing multisig operations with public keys received from t…</p> https://cve.radiocsirt.org/vuln/ghsa-h9cc-w26m-j342