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-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 |
Nimiq network-libp2p: DHT query poisoning via first-record verification failure
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.4.0, iIn handle_dht_get(), the DhtResults accumulator is only initialized when the first DHT record passes verification. If the first record fails (from a malicious DHT node), DhtResults is never created, and all subsequent valid records are discarded with "DHT inconsistent state" errors. This issue has been patched in version 1.4.0.
Published: 2026-06-09T23:45:38.719Z
Updated: 2026-06-10T18:10:17.632Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46540 |
vulnerable | 2026-07-29 00:54:59.010673 |
Nimiq light-blockchain: Light blockchain rebranch issue
MEDIUM (6.5)
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.4.0, when LightBlockchain::rebranch() adopts a fork chain whose tip is a macro block (checkpoint or election), it only updates self.head but fails to update self.macro_head, self.election_head, self.current_validators, or store the election header in the chain_store. This is in direct contrast with the full Blockchain::rebranch() at blockchain/src/blockchain/push.rs:504-518, which correctly updates all macro/election state when the new head is a macro block. After a rebranch to a macro block, the stale macro_head causes subsequent macro blocks pushed via push() to be verified against the wrong predecessor via verify_macro_successor(&this.macro_head). If the rebranch target was an election block, the stale current_validators causes every subsequent block to fail verify_validators(), completely stalling the light client's chain progression. This issue has been patched in version 1.4.0.
Published: 2026-06-09T23:45:01.847Z
Updated: 2026-06-10T13:00:12.382Z |
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.