Vulnerability Description
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 Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/nimiq/core-rs-albatross/pull/3715
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3c
FAQ
What is CVE-2026-40094?
CVE-2026-40094 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 st...
How severe is CVE-2026-40094?
CVE-2026-40094 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-40094?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.