Bind Vulnerabilities — Ubuntu Security Update (USN-8969-1)

It was discovered that Bind incorrectly handled certain DNS messages
with repeated singleton records such as SOA, CNAME, or DNAME records.
A remote attacker could possibly use this issue to cause Bind to use
excessive memory, leading to a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-75029)

It was discovered that Bind incorrectly handled cached DNSSEC proofs.
A remote attacker could possibly use this issue to cause Bind to crash,
resulting in a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-19662)

It was discovered that Bind incorrectly handled certain invalid DNSSEC
records. A remote attacker could possibly use this issue to cause Bind
to use excessive CPU resources, leading to a denial of service. This issue only affected
Ubuntu 26.10.
(CVE-2026-19668)

It was discovered that Bind incorrectly handled malformed answers on
resolvers configured to use DNS64. A remote attacker could possibly use
this issue to cause Bind to crash, resulting in a denial of service. This issue only affected
Ubuntu 26.10.
(CVE-2026-19666)

It was discovered that Bind incorrectly handled TKEY queries when no
global options block was present. A remote attacker could possibly use
this issue to cause Bind to crash, resulting in a denial of service.
This issue only affected
Ubuntu 26.10.
(CVE-2026-76163)

It was discovered that Bind incorrectly verified TSIG signatures during
zone transfers. A remote attacker could possibly use this issue to inject
unauthorized zone contents into a secondary server. This issue only affected
Ubuntu 26.10. (CVE-2026-19033)

It was discovered that Bind incorrectly handled certain NSEC wildcard
proofs. A remote attacker could possibly use this issue to forge NXDOMAIN
responses and hide the existence of wildcard records. This issue only affected
Ubuntu 26.10. (CVE-2026-19941)

It was discovered that Bind incorrectly handled DNS-over-HTTPS requests
with invalid SIG(0) records. A remote attacker could possibly use this
issue to cause Bind to crash, resulting in a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-77692)

It was discovered that Bind incorrectly handled malformed zones
containing NS or DNAME nodes above the zone origin. An attacker could
possibly use this issue to cause Bind to serve out-of-zone records as
authoritative, leading to cache poisoning. This issue only affected
Ubuntu 26.10. (CVE-2026-78301)

It was discovered that Bind incorrectly handled SVCB/HTTPS AliasMode
records referencing large numbers of ServiceMode records. A remote
attacker could possibly use this issue to cause Bind to exhaust
resources, leading to a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-81563)

It was discovered that Bind incorrectly validated NSEC3 records from
unrelated sibling zones. A remote attacker could possibly use this issue
to perform a DNSSEC downgrade attack and have forged unsigned answers
accepted. This issue only affected
Ubuntu 26.10. (CVE-2026-77119)

It was discovered that Bind incorrectly handled wildcard answers with
mixed NSEC and NSEC3 proofs. A remote attacker could possibly use this
issue to cause Bind to crash, resulting in a denial of service. This issue only affected
Ubuntu 26.10.
(CVE-2026-80274)

It was discovered that Bind incorrectly handled oversized negative
cache records. A remote attacker could possibly use this issue to cause
Bind to crash, resulting in a denial of service. This issue only affected
Ubuntu 26.10. (CVE-2026-19667)

It was discovered that Bind incorrectly handled cached trees of
SVCB/HTTPS AliasMode records. A remote attacker could possibly use this
issue to cause Bind to use excessive CPU resources, leading to a denial
of service. This issue only affected
Ubuntu 26.10. (CVE-2026-81736)

It was discovered that Bind incorrectly limited the processing of
compression pointers in inbound DNS messages. A remote attacker could
possibly use this issue to cause Bind to use excessive CPU and memory
resources, leading to a denial of service. (CVE-2026-19630)

It was discovered that Bind incorrectly serialized access to shared
GSS-TSIG security contexts. A remote attacker could possibly use this
issue to corrupt memory and execute arbitrary code. (CVE-2026-94300)

It was discovered that Bind incorrectly handled redirect zones when
used together with strict QNAME minimization. A remote attacker could
possibly use this issue to cause Bind to crash, resulting in a denial
of service. (CVE-2026-96888)

It was discovered that Bind incorrectly handled certain RPZ
configurations when processing queries with and without recursion. A
remote attacker could possibly use this issue to cause Bind to crash,
resulting in a denial of service. (CVE-2026-97313)