Summary
The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.
Security Fix(es):
* bind9: bind: BIND 9: Denial of Service via 16-bit length truncation in DNS negative cache handling (CVE-2026-19667)
* bind: BIND: Denial of Service via crafted DNSSEC reply (CVE-2026-80274)
* bind: BIND: Denial of Service via malformed DNS64 responses (CVE-2026-19666)
Bug Fix(es) and Enhancement(s):
* bind 9.16 crash with SIGSEGV (JIRA:AlmaLinux-273294)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 9
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 8 | bind9.16 | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-chroot | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-devel | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-dnssec-utils | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-doc | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-libs | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-license | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | bind9.16-utils | 32:9.16.23-0.22.el8_10.16 |
| AlmaLinux · 8 | python3-bind9.16 | 32:9.16.23-0.22.el8_10.16 |
Vulnerabilities 3
-
High 7.5
Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path
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.2…
-
High 7.5
Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`
If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 vers…
-
High 7.5
Validating resolver can abort while caching a mismatched NOQNAME proof
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 NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit.…
References
-
report
https://access.redhat.com/security/cve/CVE-2026-19666
-
report
https://access.redhat.com/security/cve/CVE-2026-19667
-
report
https://access.redhat.com/security/cve/CVE-2026-80274
-
report
https://bugzilla.redhat.com/2535435
-
report
https://bugzilla.redhat.com/2535466
-
report
https://bugzilla.redhat.com/2535477
-
advisory
https://errata.almalinux.org/8/ALSA-2026-79113.html