# CVE-2026-56444: Denial of service in Unbound

> Attackers can degrade DNS resolution service by exploiting a counter accounting error in Unbound when specific non-default timeout configurations are used.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** ALPINE-CVE-2026-56444, AZL-92955, DEBIAN-CVE-2026-56444, ECHO-c184-6fd7-ae80, GHSA-x9gf-4mqv-47hw, UBUNTU-CVE-2026-56444

## What is CVE-2026-56444?

CVE-2026-56444 is a medium-severity denial of service vulnerability in Nlnetlabs Unbound, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NLnet Labs Unbound 1.20.0 up to and including 1.25.1, when Unbound is configured with 'serve-expired: yes' and 'serve-expired-client-timeout > discard-timeout > 0' (contrary to the suggested values), the discard-timeout branch during the serve expired logic drops an aged client reply without performing the correct accounting for the number of reply addresses for the query. Other identical branches outside of serve expired perform the correct decrement. Since the counter is never decremented in such scenario, it can reach the maximum limit and new clients for duplicate in-flight queries are silently dropped resulting in degradation of resolution service. A malicious actor can exploit the vulnerability by querying the resolver for a client-controlled slow-on-demand authoritative zone that can drive the counter past the threshold. Shipped defaults for 'serve-expired-client-timeout: 1800' and 'discard-timeout: 1900' make the branch unreachable.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2026-56444?

It affects 1 product.


Products: Nlnetlabs Unbound.

## How do I fix CVE-2026-56444?

Apply the vendor's patch.

## Is CVE-2026-56444 being exploited?

There is no known exploitation of CVE-2026-56444 in the wild and no public exploit code.

## Other vulnerabilities in Nlnetlabs Unbound

- [CVE-2026-81642](https://insights.sbomify.com/CVE-2026-81642/): Heap buffer overflow and possible Remote Code Execution when digesting DNSKEY (critical 9.1)
- [CVE-2026-33278](https://insights.sbomify.com/CVE-2026-33278/): Possible arbitrary code execution during DNSSEC validation (critical 9.1)
- [CVE-2026-42944](https://insights.sbomify.com/CVE-2026-42944/): Heap overflow with multiple NSID, COOKIE, PADDING EDNS options (high 8.7)
- [CVE-2026-42959](https://insights.sbomify.com/CVE-2026-42959/): Crash during DNSSEC validation of malicious content (high 8.7)
- [CVE-2026-82717](https://insights.sbomify.com/CVE-2026-82717/): CNAME synthesis could lead to heap corruption (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56444 and fix it if it is affected.

What it is: CVE-2026-56444 is a medium-severity denial of service vulnerability in Nlnetlabs Unbound, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56444 in the wild and no public exploit code.

Affected product: Nlnetlabs Unbound. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56444/ (Markdown: https://insights.sbomify.com/CVE-2026-56444/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56444
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56444
- OSV: https://osv.dev/vulnerability/CVE-2026-56444

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56444/
Summaries are generated and may contain mistakes; the official description above is the record.