CVE-2026-44505
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 22% of all known CVEs.
References
Related Vulnerabilities
Other CWE-755 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-5638 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2020-7247 | Critical | 9.8 | 99% | KEV | Fix |
| CVE-2023-36933 | High | 7.5 | 72% | - | Fix |
| CVE-2018-0934 | High | 7.5 | 67% | - | Fix |
| CVE-2019-14287 | High | 8.8 | 64% | - | Fix |
| CVE-2019-12815 | Critical | 9.8 | 58% | - | Fix |
Common questions
How do I fix CVE-2026-44505?
No published fix for CVE-2026-44505 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-44505 being actively exploited?
Not that we know of. CVE-2026-44505 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 22% of all scored CVEs.
How severe is CVE-2026-44505?
CVE-2026-44505 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-44505
Markdown
[](https://tridentstack.com/cve/CVE-2026-44505)HTML
<a href="https://tridentstack.com/cve/CVE-2026-44505"><img src="https://tridentstack.com/cve/badge/CVE-2026-44505.svg" alt="CVE-2026-44505"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-23.