CVE-2026-40094: CWE-754: Improper Check for Unusual or Exceptional Conditions in nimiq core-rs-albatross
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.
AI Analysis
Technical Summary
In nimiq core-rs-albatross (Rust implementation of Nimiq blockchain), versions 1.3.0 and earlier accept signed PeerContact updates from untrusted peers without enforcing that the addresses list is non-empty. The PeerContactBook::known_peers function assumes each peer has at least one address and calls addresses.first().expect(), which panics if the list is empty. An attacker can exploit this by inserting a signed peer contact with an empty addresses list, causing a panic and crash of the node or RPC task. This denial-of-service vulnerability is resolved in version 1.4.0.
Potential Impact
The vulnerability can cause a denial-of-service condition by crashing the node or RPC task when the address book is accessed. There is no impact on confidentiality or integrity. The CVSS score is 4.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, user interaction needed, and impact limited to availability.
Mitigation Recommendations
Upgrade to nimiq core-rs-albatross version 1.4.0 or later, where this issue is fixed. No other mitigation is indicated. Patch status is not explicitly stated but the fix is included in version 1.4.0, so updating to this version or newer is recommended.
CVE-2026-40094: CWE-754: Improper Check for Unusual or Exceptional Conditions in nimiq core-rs-albatross
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 v3.1
Score 4.3medium
Affected software
pkg:cargo/github/nimiq/core-rs-albatrossRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In nimiq core-rs-albatross (Rust implementation of Nimiq blockchain), versions 1.3.0 and earlier accept signed PeerContact updates from untrusted peers without enforcing that the addresses list is non-empty. The PeerContactBook::known_peers function assumes each peer has at least one address and calls addresses.first().expect(), which panics if the list is empty. An attacker can exploit this by inserting a signed peer contact with an empty addresses list, causing a panic and crash of the node or RPC task. This denial-of-service vulnerability is resolved in version 1.4.0.
Potential Impact
The vulnerability can cause a denial-of-service condition by crashing the node or RPC task when the address book is accessed. There is no impact on confidentiality or integrity. The CVSS score is 4.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, user interaction needed, and impact limited to availability.
Mitigation Recommendations
Upgrade to nimiq core-rs-albatross version 1.4.0 or later, where this issue is fixed. No other mitigation is indicated. Patch status is not explicitly stated but the fix is included in version 1.4.0, so updating to this version or newer is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-09T01:41:38.536Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0eee5b7b8e1438d0bb6ce0
Added to database: 05/21/2026, 11:36:59 UTC
Last enriched: 05/21/2026, 11:37:59 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 95
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.