Vulnerability 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(&record.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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/nimiq/core-rs-albatross/pull/3716
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qw
FAQ
What is CVE-2026-44505?
CVE-2026-44505 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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/s...
How severe is CVE-2026-44505?
CVE-2026-44505 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-44505?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.