Summary
[32:9.11.36-16.14]
- Validate NSEC3 signer matches owning zone (CVE-2026-10723)
[32:9.11.36-16.12]
- Prevent accepting unsigned NSEC/NSEC3 records (CVE-2026-13204)
[32:9.11.36-16.11]
- Reject out-of-zone NSEC entries in DNSSEC validation
(CVE-2026-13321)
[32:9.11.36-16.10]
- Reject RRSIG records with invalid label counts (CVE-2026-11721)
- Add unittest check
[32:9.11.36-16.9]
- Add reference counting to cache dns_slabheaders (CVE-2026-11622)
Fixed packages 17
| Release | Package | Fixed in |
|---|---|---|
| Oracle Linux · 8 | bind | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-chroot | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-devel | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-export-devel | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-export-libs | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-libs | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-libs-lite | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-license | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-lite-devel | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-pkcs11 | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-pkcs11-devel | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-pkcs11-libs | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-pkcs11-utils | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-sdb | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-sdb-chroot | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | bind-utils | 32:9.11.36-16.el8_10.14 |
| Oracle Linux · 8 | python3-bind | 32:9.11.36-16.el8_10.14 |
Vulnerabilities 5
-
High 8.6
DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field
The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1,…
-
High 7.5
Potential memory usage beyond configured limits
A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage c…
-
High 7.5
Cache poisoning possible with label count discrepancy, RRSIG, and wildcards
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 contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker's zone, wh…
-
High 7.5
Unexpected exit in certain situations with NSEC and NSEC3 both present
If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.…
-
Medium 6.8
Incorrect acceptance of NSEC3 records
BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through …