CVE-2026-81634

Possible heap buffer overflow during DNSSEC canonicalization

Published Sep 16, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.

Analysis

AI-generated

Technical impact

A malformed domain name of 255 characters combined with a large TCP response can cause a heap buffer overflow while Unbound canonicalizes the RRSet. The missing buffer length check for the first owner name allows an attacker to overflow memory, potentially leading to code execution, denial of service, or other compromise of confidentiality and integrity on the affected system. The weakness is related to unchecked memory bounds (CWE-120/122).

Affected Systems

NLnet Labs Unbound versions up to and including 1.26.0 are vulnerable. 1.26.1. Users running any Unbound instance not yet updated to the fixed release are at risk.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity, while the EPSS score of less than 1% reflects a very low exploitation probability. The flaw can be triggered by sending a crafted DNS response over TCP to a Unbound resolver that contains a 255-character name and a large RRSet. An attacker controlling a malicious name server or tampering with the incoming response can cause a heap buffer overflow during RRSet canonicalisation, before DNSSEC validation occurs. The vulnerability is not listed in the CISA KEV catalog, but the low EPSS suggests that real‑world exploitation is unlikely at present. Nevertheless, environments that accept traffic from untrusted zones should consider the risk and apply the vendor‑supplied patch.

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
  • Ensure the resolver is not exposed to untrusted DNS traffic or limit the zones it queries
  • Apply firewall restrictions to block unsolicited DNS traffic to the resolver

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6507-1 unbound security update
Ubuntu USN Ubuntu USN USN-8946-1 Unbound vulnerabilities
Ubuntu USN Ubuntu USN USN-8946-2 Unbound vulnerabilities
History
Type Values Removed Values Added
CPEs cpe:2.3:a:nlnetlabs:unbound:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Nlnetlabs
Nlnetlabs unbound
Vendors & Products Nlnetlabs
Nlnetlabs unbound
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
Title Possible heap buffer overflow during DNSSEC canonicalization
Weaknesses CWE-122
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-122

    Heap-based Buffer Overflow

Sources

Status
PUBLISHED
Assigner
NLnet Labs
Published
Updated
Sep 16, 2026, 2:32 PM
Reserved
Sep 7, 2026, 2:06 PM
Status
Analyzed
Published
Sep 16, 2026, 9:17 AM
Modified
Sep 23, 2026, 7:51 PM
Severity
Important
Public date
Sep 16, 2026, 8:30 AM