On this page (6 sections)
Ubuntu published USN-8946-2 on 2026-11-10. According to that notice, it is the corresponding update for Ubuntu 26.10 to USN-8946-1, which fixed Unbound vulnerabilities in Ubuntu 26.04 LTS and older releases. The issues affect Unbound, the recursive DNS resolver, and include a heap buffer overflow that carries a high CVSS score.
If you run Unbound as the resolver for a server, a hosting platform, a mail system or an office network, this is worth a quick version check. The impact described by the sources is denial of service: a resolver that crashes or stalls takes name resolution down for everything that depends on it.
What happened
NLnet Labs released Unbound 1.26.1, which its advisories name as the fix for three issues: CVE-2026-81634, CVE-2026-80225 and CVE-2026-85501. The CVE records show all three were published on 2026-09-16, and all affect Unbound up to and including 1.26.0.
The Ubuntu notice lists these three plus a fourth, CVE-2026-50252, which it describes as incorrect handling of outgoing network ports that could let a remote attacker crash Unbound. The research does not include upstream details for that one, so this article does not analyze it. The Ubuntu text available to us is truncated, so read the full notice for any further entries and for the fixed package versions.
The flaws in plain terms
CVE-2026-81634: heap buffer overflow
When Unbound builds a canonical form of a set of DNS records, it checks that the data fits a buffer. According to the NLnet Labs advisory, the first owner name was missing from that length check, so a 255-length query name combined with a large TCP response can overflow a heap buffer. The advisory notes that canonicalisation happens before DNSSEC validation, and says an attacker operating a malicious name server, or tampering with a response on its way to Unbound, can trigger the flaw. Ubuntu describes the outcome as a possible crash and denial of service. The sources do not claim code execution.
CVE-2026-80225: TCP and DNS-over-TLS starvation
Unbound had no limit on consecutive reads from a single TCP or DoT connection. Per the vendor advisory, a client that streams a sustained flow of distinct uncached names can monopolize one worker's entire event loop while its writes stay ahead of the drain. The fix limits consecutive reads per connection, similar to the existing UDP logic. Ubuntu notes this issue only affected Ubuntu 26.04 LTS, 24.04 LTS, 22.04 LTS and 20.04 LTS.
CVE-2026-85501: the 'ReTrap' DNSSEC complexity attacks
Researchers studied algorithmic complexity attacks on DNSSEC under the name ReTrap, where malicious zones cause degradation of service by forcing a resolver to spend resources validating records. The advisory says four variants are relevant to Unbound:
- TagTrap: many mismatched DNSKEY, RRSIG and DS records abuse the (Zone, Algo, KeyTag) matching. Fix: limit DNSKEY tag matches to 256.
- DelegationTrap: validating deeply nested domains from the root down is costly. Fix: limit attempted DS and DNSKEY operations to 32 each, configurable with val-hash-attempts and val-validation-attempts.
- NsecTrap: excessive invalid NSEC records each need validation. Fix: limit NSEC or NSEC3 validations to 8 per message, with no validator restart if exceeded.
- AdditionalTrap: Unbound by default also validated the ADDITIONAL section. Fix: val-clean-additional is now off by default, disabling DNSSEC validation of additional section RRsets.
Who is realistically exposed
Any host running Unbound 1.26.0 or earlier is in the affected range. What the advisories say about triggers is limited. The TCP/DoT starvation issue requires a client that can sustain a stream of distinct uncached names over a TCP or DoT connection, so resolvers that accept such connections from clients you do not control are the natural concern. The overflow requires a malicious name server or tampering with a response, and the DNSSEC complexity issues require malicious zones serving crafted responses. The advisories do not say how an attacker would get a resolver to contact such servers, so as a practical judgment, treat any resolver that answers lookups for users or applications you do not fully control as worth patching promptly. A resolver that only serves your own servers is likely lower risk but is still in the affected range.
Exploitation status is unconfirmed. The CVE records show no CISA KEV entry, and the GitHub advisories show an EPSS score of about 0.48% (42nd percentile), which is a probability estimate for the next 30 days and not an assurance either way.
How to check your version
This standard, read-only command prints the Unbound version on a system where the binary is installed. An upstream version of 1.26.0 or lower is in the affected range.
unbound -VOn Debian and Ubuntu, this read-only command shows the installed package version and the candidate version available from your repositories. Compare it with the fixed package version listed in the full Ubuntu notice for your release.
apt-cache policy unboundWhat to do now
- Find every system running Unbound, including DNS servers, containers and appliances that bundle it.
- Run unbound -V and apt-cache policy unbound to see which are on 1.26.0 or earlier and which package version is installed.
- On Ubuntu, read USN-8946-1 and USN-8946-2 for your release, note the fixed package version, and update to it.
- On other systems, upgrade to Unbound 1.26.1 through your distribution or from NLnet Labs. If you build from source, the vendor provides patches tested on 1.26.0.
- Restart Unbound after updating and confirm name resolution works.
- If you set val-clean-additional or the validation attempt limits yourself, review them against the new defaults.
- Review who can query your resolver and limit access to the clients that need it.
On Ubuntu, the following commands update only the Unbound package and then restart the service. Afterwards, run apt-cache policy unbound again and confirm the installed version matches the fixed version in the notice for your release.
sudo apt update && sudo apt install --only-upgrade unbound
sudo systemctl restart unboundDetection and monitoring
The sources describe symptoms rather than indicators of compromise, so watch for the effects: Unbound crashing or restarting unexpectedly, one worker pinned at high CPU, slow or failing lookups, and unusual volumes of distinct uncached names over TCP or DoT from a single client. Alert on resolver process restarts and on DNS lookup latency from your own servers.
DNS problems often show up first as outages or certificate and record changes. Webforta Monitor can watch uptime, certificates and DNS records for your public sites, which helps you notice when resolution trouble affects them. For background, see DDoS protection basics and uptime monitoring explained.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
- CVE-2026-80225 - GitHub Advisory Database
- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-80225.txt
- CVE-2026-81634 - GitHub Advisory Database
- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-81634.txt
- CVE-2026-85501 - GitHub Advisory Database
- https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-85501.txt
- USN-8946-2: Unbound vulnerabilities
