UBUNTU-CVE-2026-19666: High severity ubuntu/bind9 vulnerability
On a resolver configured to use dns64, if an applicable answer from the authoritative server is malformed in a specific way, the resolver named process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.9.5.dfsg-3ubuntu0.19+esm15 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.10.3.dfsg.P4-8ubuntu1.19+esm11 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.11.3+dfsg-1ubuntu1.19+esm6 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.18.30-0ubuntu0.20.04.2+esm3 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.18.39-0ubuntu0.22.04.7 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.18.39-0ubuntu0.24.04.8 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.20.24-1ubuntu3.1 - Upgrade
Upgrade
ubuntu/bind9to a version that resolves this vulnerability.Fixed in 1:9.20.24-1ubuntu0.4
Event History
Frequently Asked Questions
Which deployments are exposed to this denial-of-service condition?
Resolvers running the BIND named process are affected when they are configured to use dns64 and fall within the listed affected BIND version ranges. The provided information does not establish that deployments without dns64 are affected.
What must an attacker do to trigger the failure?
An attacker needs to cause the resolver to process an applicable authoritative-server answer that is malformed in a specific way. No authentication or user interaction is required according to the supplied severity vector.
What is the operational impact if exploitation succeeds?
The named resolver process exits unexpectedly, causing a denial of service until the service is restarted or otherwise recovered.