CVE-2026-44390
Denial of Service in Unbound DNS Server
Publication date: 2026-05-20
Last updated on: 2026-05-20
Assigner: NLnet Labs
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nlnet_labs | unbound | to 1.25.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-407 | An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-44390 is a vulnerability in Unbound, a DNS resolver, affecting versions up to and including 1.25.0. It occurs when Unbound handles replies containing very large Resource Record sets (RRsets) that require name compression. If the RRsets contain records that do not share a suffix above the root, Unbound enters a code path where it fails to increment the compression counter properly. This causes Unbound to spend excessive time applying name compression, potentially locking the CPU until the entire packet is processed.
How can this vulnerability impact me? :
This vulnerability can lead to degraded performance of the Unbound DNS resolver and can eventually cause a denial of service (DoS) in well-orchestrated attacks. An attacker can exploit this by sending specially crafted DNS responses with very large RRsets that trigger the excessive name compression processing, effectively locking the CPU and disrupting normal DNS resolution.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Unbound to version 1.25.1 or later, which contains a patch that fixes the issue by properly incrementing the compression counter regardless of the compression tree lookup.
Alternatively, if upgrading is not immediately possible, you can manually apply the patch provided for Unbound 1.25.0 to address the vulnerability.