Bugs fixes in "bind9"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2026-77119 | A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged un | 2026-10-14 |
| CVE | CVE-2026-81563 | A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may fail to properly deallocate int | 2026-10-14 |
| CVE | CVE-2026-78301 | A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a | 2026-10-14 |
| CVE | CVE-2026-19941 | An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an u | 2026-10-14 |
| CVE | CVE-2026-19662 | An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC- | 2026-10-14 |
| CVE | CVE-2026-19666 | On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` | 2026-10-14 |
| CVE | CVE-2026-75029 | In a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is th | 2026-10-14 |
| CVE | CVE-2026-19667 | If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negativ | 2026-10-14 |
| CVE | CVE-2026-81736 | If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree, the resolver will spend dispropo | 2026-10-14 |
| CVE | CVE-2026-19033 | For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with | 2026-10-14 |
| CVE | CVE-2026-80274 | If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed | 2026-10-14 |
| CVE | CVE-2026-77119 | A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged un | 2026-10-14 |
| CVE | CVE-2026-81563 | A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may fail to properly deallocate int | 2026-10-14 |
| CVE | CVE-2026-78301 | A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a | 2026-10-14 |
| CVE | CVE-2026-19941 | An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an u | 2026-10-14 |
| CVE | CVE-2026-19662 | An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC- | 2026-10-14 |
| CVE | CVE-2026-19666 | On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` | 2026-10-14 |
| CVE | CVE-2026-75029 | In a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is th | 2026-10-14 |
| CVE | CVE-2026-81736 | If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree, the resolver will spend dispropo | 2026-10-14 |
| CVE | CVE-2026-19667 | If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negativ | 2026-10-14 |
About
-
Send Feedback to @ubuntu_updates
