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.
Published: 2026-07-22
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In Unbound versions 1.20.0 through 1.25.1, a configuration that enables serve‑expired with serve‑expired‑client‑timeout greater than discard‑timeout results in a counter that is never decremented when a client reply is discarded. The counter can overflow, causing duplicate in‑flight queries from new clients to be silently dropped. An attacker can trigger this by directing the resolver to handle an authoritative zone that responds slowly, forcing the counter past its threshold and degrading DNS resolution service.

Affected Systems

The vulnerability affects NLnet Labs Unbound running any version from 1.20.0 to 1.25.1. The issuing patch is included in version 1.25.2 and later.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity, and the EPSS score is < 1%. The vulnerability is not listed in CISA's KEV. Exploitation requires a server to be mis‑configured with the described timeout settings; an attacker then exploits the service by sending queries that reference a slow‑responding authoritative zone. Because the issue is limited to servers with those settings, the risk is lower for correctly configured installations but can still lead to a denial of service for affected deployments.

Generated by OpenCVE AI on August 3, 2026 at 23:43 UTC.

Remediation

Vendor Solution

This issue is fixed starting with version 1.25.2


OpenCVE Recommended Actions

  • Upgrade Unbound to version 1.25.2 or newer.
  • Verify that serve‑expired is disabled or that serve‑expired‑client‑timeout and discard‑timeout are configured per the vendor’s recommendations to avoid the counter overflow condition.
  • Implement query rate limiting or protect against slow‑zone amplification to reduce the impact of malicious query traffic.

Generated by OpenCVE AI on August 3, 2026 at 23:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 30 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Low


Tue, 28 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
First Time appeared Nlnetlabs
Nlnetlabs unbound
Vendors & Products Nlnetlabs
Nlnetlabs unbound

Wed, 22 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 22 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
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.
Title Degradation of resolution service when 'discard-timeout' and 'serve-expired-client-timeout' are combined in unusual configuration
Weaknesses CWE-772
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

Nlnetlabs Unbound
cve-icon MITRE

Status: PUBLISHED

Assigner: NLnet Labs

Published:

Updated: 2026-07-22T13:58:09.702Z

Reserved: 2026-06-22T12:35:21.345Z

Link: CVE-2026-56444

cve-icon Vulnrichment

Updated: 2026-07-22T13:57:57.751Z

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-07-22T14:17:22.203

Modified: 2026-07-24T13:43:15.783

Link: CVE-2026-56444

cve-icon Redhat

Severity : Low

Publid Date: 2026-07-22T13:10:34Z

Links: CVE-2026-56444 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T23:45:06Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime