Bugs fixes in "bind9"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| 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-11-06 |
| 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-11-06 |
| 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-11-06 |
| CVE | CVE-2026-11721 | It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is con | 2026-11-06 |
| CVE | CVE-2026-5950 | An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling, enabling a remote unauthenticated atta | 2026-11-06 |
| CVE | CVE-2026-5946 | Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or ` | 2026-11-06 |
| CVE | CVE-2026-3592 | BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone | 2026-11-06 |
| CVE | CVE-2026-3039 | BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving an | 2026-11-06 |
| CVE | CVE-2026-1519 | Excessive NSEC3 iterations cause high CPU load during insecure delegation validation | 2026-11-06 |
| CVE | CVE-2025-40780 | Cache poisoning due to weak PRNG | 2026-11-06 |
| CVE | CVE-2025-40778 | Cache poisoning attacks with unsolicited RRs | 2026-11-06 |
| CVE | CVE-2025-8677 | Resource exhaustion via malformed DNSKEY handling | 2026-11-06 |
| Launchpad | 2126464 | Backport of bind9 for resolute, noble, and jammy | 2026-11-06 |
| 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-11-06 |
| 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-11-06 |
| 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-11-06 |
| CVE | CVE-2026-11721 | It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is con | 2026-11-06 |
| CVE | CVE-2026-5950 | An unbounded resend loop vulnerability exists in the BIND 9 resolver state machine during bad-server handling, enabling a remote unauthenticated atta | 2026-11-06 |
| CVE | CVE-2026-5946 | Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or ` | 2026-11-06 |
| CVE | CVE-2026-3592 | BIND resolvers are vulnerable to an amplified resource consumption/exhaustion attack. If a victim resolver makes a query to a specially crafted zone | 2026-11-06 |
About
-
Send Feedback to @ubuntu_updates