Core Rs Albatross
Approved changes feed: RSS · Atom
cpe:2.3:a:nimiq:core-rs-albatross:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Nimiq (a6c6d398-2780-5e77-a82f-ca37478d870d) |
|---|---|
| Product | Core Rs Albatross (24b78fe4-6c1b-5189-841a-5523f30d2254) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/nimiq/core-rs-albatross |
purl2cpe | 2026-06-01 10:12:23.280882 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54541 |
vulnerable | 2026-09-16 04:33:28.741198 |
Nimiq: Panic in TrieProof::verify via child_index unwrap on equal-length keys
LOW (3.7)
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to 1.6.0, a malicious state-sync peer can crash a syncing node by sending a crafted TrieChunk proof containing two TrieProofNode values with identical keys. TrieProof::verify calls TrieProofNode::child_index in primitives/src/trie/trie_proof_node.rs, where is_prefix_of accepts equal keys and KeyNibbles::get is called at the key length, returns None, and is unconditionally unwrapped. Untrusted ResponseChunk data reaches commit_chunks, put_chunk, and proof.verify before cryptographic proof validation, so the attacker does not need a valid proof. Exploitation requires the attacker to be selected as the victim's sync peer during state sync, and the resulting panic is transient because the node restarts and resynchronizes. This issue is fixed in version 1.6.0.
Published: 2026-09-14T15:30:51.319Z
Updated: 2026-09-16T15:13:43.511Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54542 |
vulnerable | 2026-09-16 04:33:28.475931 |
Nimiq: Out-of-bounds panic in KeyNibbles::Add from oversized child suffix in a deserialized proof
LOW (3.7)
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to 1.6.0, a malicious state-sync peer can crash a syncing node by sending a crafted TrieChunk whose proof contains a TrieNodeChild suffix that is individually valid but exceeds the 63-byte KeyNibbles backing array when combined with the parent key. KeyNibbles::Add in primitives/src/key_nibbles.rs performs the combined slice operation without checking the total length, and the input reaches put_chunk, TrieNodeChild::key, and TrieNodeChild::is_stump before proof.verify, so the attacker does not need a valid cryptographic proof. Exploitation requires the attacker to be selected as the victim's sync peer during state sync. The resulting out-of-bounds panic is transient because the node restarts and resynchronizes. This issue is fixed in version 1.6.0.
Published: 2026-09-14T15:29:45.070Z
Updated: 2026-09-14T20:07:10.225Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46545 |
vulnerable | 2026-07-29 00:54:59.011625 |
nimiq-primitives: Panic DoS in trie chunk processing via ROOT-keyed item
HIGH (7.5)
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.5.0, a remote, unauthenticated denial-of-service vulnerability in MerkleRadixTrie::put_chunk allows any state-sync peer to crash any node performing state synchronization (freshly joining nodes and recovering nodes). This issue has been patched in version 1.5.0.
Published: 2026-06-09T23:47:51.072Z
Updated: 2026-06-10T14:38:24.123Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46543 |
vulnerable | 2026-07-29 00:54:59.011030 |
nimiq-blockchain: Genesis batch set request
MEDIUM (5.3)
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.5.0, a remote peer can crash any full node by sending a RequestBatchSet message containing the genesis block's hash. The handler calls get_epoch_chunks which iterates backwards through macro blocks using Policy::macro_block_before. When it reaches the genesis block number, macro_block_before panics with "No macro blocks before genesis block". This issue has been patched in version 1.5.0.
Published: 2026-06-09T23:47:32.019Z
Updated: 2026-06-10T16:32:15.916Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46542 |
vulnerable | 2026-07-29 00:54:59.010920 |
nimiq-keys: Denial of service in Ed25519 multisig delinearization via invalid curve points
MEDIUM (4.3)
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.
Published: 2026-06-09T23:46:21.832Z
Updated: 2026-06-10T13:11:58.177Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46541 |
vulnerable | 2026-07-29 00:54:59.010800 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46540 |
vulnerable | 2026-07-29 00:54:59.010673 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46539 |
vulnerable | 2026-07-29 00:54:59.010276 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44505 |
vulnerable | 2026-07-29 00:52:14.408718 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40094 |
vulnerable | 2026-06-08 08:01:19.884891 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40093 |
vulnerable | 2026-06-08 08:01:19.883355 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40092 |
vulnerable | 2026-06-08 08:01:19.882889 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-35468 |
vulnerable | 2026-06-08 07:59:14.037015 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34069 |
vulnerable | 2026-06-08 07:59:11.734822 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34061 |
vulnerable | 2026-06-08 07:59:11.724317 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33184 |
vulnerable | 2026-06-08 07:59:09.304881 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32605 |
vulnerable | 2026-06-08 07:57:17.742740 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-28402 |
vulnerable | 2026-06-08 07:55:15.253457 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-47270 |
vulnerable | 2026-06-08 07:27:09.872297 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.