{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44505 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44505 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44505 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44505 and fix it if it is affected.\n\nWhat it is: CVE-2026-44505 is a medium-severity denial of service vulnerability in nimiq core-rs-albatross, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44505 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-44505/ (Markdown: https://insights.sbomify.com/CVE-2026-44505/index.md)","id":"CVE-2026-44505","markdown":"https://insights.sbomify.com/CVE-2026-44505/index.md","name":"CVE-2026-44505","record":{"aliases":["GHSA-g39c-jcgg-qwvr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust networking library","requires_auth":"none","summary":"An untrusted peer can cause indefinite hangs in DHT queries by triggering verifier errors, leading to denial of service in Nimiq network-libp2p.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. network-libp2p handles kad get-record query progress in handle_dht_get (network-libp2p/src/swarm.rs). Prior to version 1.4.0, when a peer returns a FoundRecord, the code verifies the record via dht_verifier.verify(\u0026record.record). On verifier error, handle_dht_get logs and returns early without completing the oneshot used by Network::dht_get, and without cleaning up per-query bookkeeping. Later query progress can hit the \"DHT inconsistent state\" path and also return without cleanup. Because Network::dht_get awaits the oneshot without a timeout, the caller future can hang indefinitely. This issue has been patched 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 network-libp2p: Untrusted peer can wedge DHT","id":"CVE-2026-44505","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":"Medplum - Exposure of OAuth client secret via dynamic registration endpoint in self-hosted configurations","id":"CVE-2026-44506"},"packages":[],"prev":{"headline":"Aegra: Cross-user run injection in /threads/{thread_id}/runs (IDOR)","id":"CVE-2026-44504"},"products":["core-rs-albatross"],"published":"2026-06-09","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-10","vendors":["nimiq"]},"summary":"An untrusted peer can cause indefinite hangs in DHT queries by triggering verifier errors, leading to denial of service in Nimiq network-libp2p.","url":"https://insights.sbomify.com/CVE-2026-44505/"}