{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-40094 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40094 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40094 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40094 and fix it if it is affected.\n\nWhat it is: CVE-2026-40094 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40094 in the wild and no public exploit code.\n\nAffected product: nimiq core-rs-albatross. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40094/ (Markdown: https://insights.sbomify.com/CVE-2026-40094/index.md)","id":"CVE-2026-40094","markdown":"https://insights.sbomify.com/CVE-2026-40094/index.md","name":"CVE-2026-40094","record":{"aliases":["GHSA-c45m-6x25-3cjq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust blockchain library","requires_auth":"none","summary":"An untrusted peer can crash the Nimiq blockchain node by submitting a peer contact with an empty address list, causing a panic during address book generation.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"nimiq-blockchain: network-libp2p untrusted peer can crash address book via empty peer contact addresses","id":"CVE-2026-40094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"immich: Open Redirect via Shared Album name","id":"CVE-2026-40096"},"packages":[],"prev":{"headline":"nimiq-blockchain is missing a wall-clock upper bound on block timestamps","id":"CVE-2026-40093"},"products":["core-rs-albatross"],"published":"2026-05-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-21","vendors":["nimiq"]},"summary":"An untrusted peer can crash the Nimiq blockchain node by submitting a peer contact with an empty address list, causing a panic during address book generation.","url":"https://insights.sbomify.com/CVE-2026-40094/"}