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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
This issue is fixed starting with version 1.26.1
Workaround
No workaround given by the vendor.
References
History
Wed, 16 Sep 2026 08:45:00 +0000
| 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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: NLnet Labs
Published:
Updated: 2026-09-16T08:30:15.428Z
Reserved: 2026-09-07T14:06:21.967Z
Link: CVE-2026-81634
No data.
Status : Received
Published: 2026-09-16T09:17:06.210
Modified: 2026-09-16T09:17:06.210
Link: CVE-2026-81634
No data.
OpenCVE Enrichment
No data.
Weaknesses