CVE-2026-40094: fallo de gravedad media en nimiq core-rs-albatross
nimiq-blockchain: network-libp2p untrusted peer can crash address book via empty peer contact addresses
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 4.3epss 0.3%
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In versions 1.3.0 and prior, network-libp2p discovery accepts signed PeerContact updates from untrusted peers and stores them in a peer contact book, eventually leading to address book crash. A PeerContact can legally contain an empty addresses list (no intrinsic validation enforces non-empty). Later, PeerContactBook::known_peers builds an address book by taking addresses.first().expect("every peer should have at least one address"). If the attacker has inserted a signed peer contact with addresses=[], any call to get_address_book (RPC/web client) can panic and crash the node/RPC task depending on panic settings. This issue has been fixed in version 1.4.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Productos afectados
nimiq · core-rs-albatrossCVEs relacionadas — nimiq core-rs-albatross
En el mismo producto, de las más peligrosas a las menos.
CVE-2025-47270HIGHnimiq-network-libp2p Uncontrolled Resource Consumption vulnerabilityEPSS 0.7%CVE-2026-40092HIGHnimiq-keys: Unchecked Ed25519 signature length in TaggedPublicKey::verify causes remote node panic via DHTEPSS 0.6%CVE-2026-46369HIGHNimiq: Validity store off by one errorEPSS 0.5%CVE-2026-35468MEDIUMnimiq/core-rs-albatross: Panic in history index request handlers when a full node runs without the history indexEPSS 0.5%CVE-2026-33184HIGHnimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panicEPSS 0.5%CVE-2026-32605HIGHNimiq: Remote crash via off-by-one signer bounds check in proposal bufferEPSS 0.5%