{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-40094","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-04-09T01:41:38.536Z","datePublished":"2026-05-20T21:27:40.862Z","dateUpdated":"2026-05-21T12:21:16.840Z"},"containers":{"cna":{"title":"nimiq-blockchain: network-libp2p untrusted peer can crash address book via empty peer contact addresses","problemTypes":[{"descriptions":[{"cweId":"CWE-754","lang":"en","description":"CWE-754: Improper Check for Unusual or Exceptional Conditions","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":4.3,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"}}],"references":[{"name":"https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq","tags":["x_refsource_CONFIRM"],"url":"https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq"},{"name":"https://github.com/nimiq/core-rs-albatross/pull/3715","tags":["x_refsource_MISC"],"url":"https://github.com/nimiq/core-rs-albatross/pull/3715"},{"name":"https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0","tags":["x_refsource_MISC"],"url":"https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0"}],"affected":[{"vendor":"nimiq","product":"core-rs-albatross","versions":[{"version":"< 1.4.0","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-05-20T21:27:40.862Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-c45m-6x25-3cjq","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-05-21T12:21:08.211423Z","id":"CVE-2026-40094","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2026-05-21T12:21:16.840Z"}}]}}