Description
In NLnet Labs Unbound 1.13.2 up to and including 1.26.1, a vulnerability in ZONEMD configured zones (zonemd-check: yes) which are located below (but not at) a trust anchor allow for an attack window where (tampered with) zone contents are served (or stored to disk) prior to the ZONEMD integrity check. This is caused by the needed DS/DNSKEY asynchronous resolution that needs to happen before the ZONEMD check completes. If a zonefile is written to disk (zonefile: option) while the ZONEMD check failed, the tampered data are reloaded on startup and available until ZONEMD verification concludes again. If verification fails, the data is not served any more but still persists on disk for future reloads.
Published: 2026-09-16
Score: 4.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: DNS data integrity compromise
Action: Apply Patch
AI Analysis

Impact

In Unbound versions 1.13.2 through 1.26.1, the timing between asynchronous resolution of DS/DNSKEY records and the ZONEMD integrity check can allow an attacker who can alter zone contents before the check completes to serve or persist tampered DNS records. The flaw arises because the zone file may be written to disk or reloaded while the ZONEMD verification is still pending, enabling the compromised data to be returned until verification finally succeeds. This results in a loss of DNS data authenticity and integrity.

Affected Systems

NLnet Labs Unbound 1.13.2 to 1.26.1 with zonemd-check enabled on zones located below (but not at) a trust anchor.

Risk and Exploitability

The CVSS score of 4.4 indicates medium severity. The EPSS score of < 1% indicates a very low but non-zero exploitation probability. The vulnerability is not listed in CISA KEV. This flaw requires an attacker to modify zone content before the ZONEMD check completes or to prevent the check from finishing, which suggests a narrow attack surface; however, affected deployments should monitor for this timing window and the persistence of tampered data until validation succeeds.

Generated by OpenCVE AI on September 18, 2026 at 10:51 UTC.

Remediation

Vendor Solution

This issue is fixed starting with version 1.26.1


OpenCVE Recommended Actions

  • Upgrade Unbound to version 1.26.1 or later, which fixes the ZONEMD verification timing issue.
  • Ensure that the zonemd-check option remains enabled and that zones are configured to be located under a trust anchor to satisfy the intended validation order.
  • Verify that zone files are not being written to disk during a pending ZONEMD check; coordinate startup scripts or file reload mechanisms to prevent writes until after verification passes.
  • Monitor Unbound logs for repeated “ZONEMD verification failed” messages and reloads of stale zones, and review any anomalous zone file modifications.

Generated by OpenCVE AI on September 18, 2026 at 10:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6507-1 unbound security update
History

Wed, 23 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:nlnetlabs:unbound:*:*:*:*:*:*:*:*

Thu, 17 Sep 2026 21:00:00 +0000

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

Wed, 16 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Wed, 16 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

threat_severity

Moderate


Wed, 16 Sep 2026 08:45:00 +0000

Type Values Removed Values Added
Description In NLnet Labs Unbound 1.13.2 up to and including 1.26.1, a vulnerability in ZONEMD configured zones (zonemd-check: yes) which are located below (but not at) a trust anchor allow for an attack window where (tampered with) zone contents are served (or stored to disk) prior to the ZONEMD integrity check. This is caused by the needed DS/DNSKEY asynchronous resolution that needs to happen before the ZONEMD check completes. If a zonefile is written to disk (zonefile: option) while the ZONEMD check failed, the tampered data are reloaded on startup and available until ZONEMD verification concludes again. If verification fails, the data is not served any more but still persists on disk for future reloads.
Title Possible ZONEMD verification bypass window
Weaknesses CWE-345
References
Metrics cvssV3_1

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


Subscriptions

Nlnetlabs Unbound
cve-icon MITRE

Status: PUBLISHED

Assigner: NLnet Labs

Published:

Updated: 2026-09-16T14:33:24.961Z

Reserved: 2026-09-07T14:06:21.947Z

Link: CVE-2026-77955

cve-icon Vulnrichment

Updated: 2026-09-16T14:33:22.241Z

cve-icon NVD

Status : Analyzed

Published: 2026-09-16T09:17:05.780

Modified: 2026-09-23T20:19:28.093

Link: CVE-2026-77955

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-16T08:29:39Z

Links: CVE-2026-77955 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-18T11:00:09Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition