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.
CVE-2026-44505
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 21.6%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
June 10, 2026
Advisory Details (3)
Auto-updated Jun 13, 2026Untrusted peer can wedge DHT · Advisory · nimiq/core-rs-albatross · GitHub
https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvrMainnet 1.4.0
Patch available: nimiq/core-rs-albatross v1.4.0
https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0Fix DHT GetRecord query wedge on untrusted peer responses
Patch available: nimiq/core-rs-albatross v1.4.0 (PR #3716 merged 2026-04-22)
https://github.com/nimiq/core-rs-albatross/pull/3716Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 62× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-16 00:15 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:53 UTCEG score recompute
- 2026-07-13 23:53 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 01:10 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:35 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 21:20 UTCEG score recompute
- 2026-07-09 23:06 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 21:00 UTCEG score recompute
- 2026-07-07 22:24 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 11:58 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 12:48 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 08:36 UTCEG score recompute
- 2026-07-02 10:15 UTCEG score recompute
Show 51 moreShow fewer
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 12:00 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 13:45 UTCEG score recompute
- 2026-06-29 14:34 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 16:18 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:02 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:47 UTCEG score recompute
- 2026-06-25 21:32 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 23:15 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 01:00 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 02:45 UTCEG score recompute
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 04:23 UTCEG score recompute
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 05:32 UTCEG score recompute
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 07:14 UTCEG score recompute
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-19 08:23 UTCEG score recompute
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 09:44 UTCEG score recompute
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 11:29 UTCEG score recompute
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 13:15 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 14:51 UTCEG score recompute
- 2026-06-14 16:35 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 18:19 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 20:04 UTCEG score recompute
- 2026-06-11 21:48 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 23:33 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 01:18 UTCEG score recompute
- 2026-06-10 01:17 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-44505?
When was CVE-2026-44505 disclosed?
Is CVE-2026-44505 actively exploited?
What is the CVSS score of CVE-2026-44505?
How do I remediate CVE-2026-44505?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-44505
Is Your Infrastructure Affected by CVE-2026-44505?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.