OESA-2026-4607: bind security update
BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly. Security Fix(es):
A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged unsigned answer through. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.(CVE-2026-77119)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/bindto a version that resolves this vulnerability.Fixed in 9.18.21-15.oe2403sp3
Event History
Frequently Asked Questions
Which BIND deployments are affected?
Affected versions are BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
What does an attacker need to exploit this issue?
An attacker needs to provide a validly signed NSEC3 record from an unrelated sibling zone. The flaw can cause it to be accepted as proof of insecurity for a secure delegation, allowing a forged unsigned DNS answer to pass through.