Summary
[9.16.23-40.0.1.el9_8.8]
- Fix warning when changing device file permissions [Orabug: 36518580]
[32:9.16.23-40.8]
- Fix NSEC3 signer validation (CVE-2026-10723)
[32:9.16.23-40.7]
- Fix CVE-2026-13321: reject out-of-zone NSEC next owner names
[32:9.16.23-40.6]
- Fix RPZ name-too-long wildcard expansion (CVE-2026-11331)
[32:9.16.23-40.5]
- Fix dns_rdataset_addnoqname() accepting unsigned NSEC/NSEC3
(CVE-2026-13204)
[32:9.16.23-40.4]
- Fix dnssec-signzone and RRSIG wildcard validation (CVE-2026-11721)
[32:9.16.23-40.3]
- Prevent cache memory exhaustion under sustained attack
(CVE-2026-11622, RHEL-213397)
[32:9.16.23-40.2]
- Fix GSS-API resource leak (CVE-2026-3039)
- Invalid handling of CLASS != IN (CVE-2026-5946)
[32:9.16.23-40.1]
- Prevent Denial of Service via maliciously crafted DNSSEC-validated zone
(CVE-2026-1519)
Fixed packages 10
| Release | Package | Fixed in |
|---|---|---|
| Oracle Linux · 9 | bind | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-chroot | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-devel | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-dnssec-doc | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-dnssec-utils | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-doc | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-libs | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-license | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | bind-utils | 32:9.16.23-40.0.1.el9_8.8 |
| Oracle Linux · 9 | python3-bind | 32:9.16.23-40.0.1.el9_8.8 |
Vulnerabilities 6
-
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 wildcard CNAME RPZ policy bypass
An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It…
-
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 …