{"schema_version":"1.7.2","id":"OESA-2026-3290","modified":"2026-08-07T02:44:23Z","published":"2026-08-07T02:44:23Z","upstream":["CVE-2026-10723","CVE-2026-10822","CVE-2026-11331","CVE-2026-11605","CVE-2026-11622","CVE-2026-11721","CVE-2026-12617","CVE-2026-13204","CVE-2026-13321"],"summary":"bind security update","details":"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.\r\n\r\nSecurity Fix(es):\n\nBIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses.\nThis 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 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-10723)\n\nIf BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.\n\nBIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing.\nThis 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-10822)\n\nAn 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 also may lead to an unexpected exit of the BIND 9 software.\nThis issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11331)\n\nThe issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but superfluous RRSIG records causes the validator to waste disproportionate CPU time.\nThis issue affects BIND 9 versions 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11605)\n\nA 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 can be orders of magnitude beyond the limit configured in the `max-cache-size` parameter.\nThis 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, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11622)\n\nIt 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, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set `synth-from-dnssec yes;` (which is the default).\nThis 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, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-11721)\n\nThe issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, `named` may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur.\nThis issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-12617)\n\nIf 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.\nThis 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, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-13204)\n\nThe BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone.\nThis 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, and 9.20.9-S1 through 9.20.24-S1.(CVE-2026-13321)","affected":[{"package":{"ecosystem":"openEuler:24.03-LTS-SP4","name":"bind","purl":"pkg:rpm/openEuler/bind&distro=openEuler-24.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.21-4.oe2403sp4"}]}],"ecosystem_specific":{"aarch64":["bind-9.20.21-4.oe2403sp4.aarch64.rpm","bind-chroot-9.20.21-4.oe2403sp4.aarch64.rpm","bind-debuginfo-9.20.21-4.oe2403sp4.aarch64.rpm","bind-debugsource-9.20.21-4.oe2403sp4.aarch64.rpm","bind-devel-9.20.21-4.oe2403sp4.aarch64.rpm","bind-dnssec-utils-9.20.21-4.oe2403sp4.aarch64.rpm","bind-libs-9.20.21-4.oe2403sp4.aarch64.rpm","bind-utils-9.20.21-4.oe2403sp4.aarch64.rpm"],"noarch":["bind-dnssec-doc-9.20.21-4.oe2403sp4.noarch.rpm","bind-license-9.20.21-4.oe2403sp4.noarch.rpm"],"src":["bind-9.20.21-4.oe2403sp4.src.rpm"],"x86_64":["bind-9.20.21-4.oe2403sp4.x86_64.rpm","bind-chroot-9.20.21-4.oe2403sp4.x86_64.rpm","bind-debuginfo-9.20.21-4.oe2403sp4.x86_64.rpm","bind-debugsource-9.20.21-4.oe2403sp4.x86_64.rpm","bind-devel-9.20.21-4.oe2403sp4.x86_64.rpm","bind-dnssec-utils-9.20.21-4.oe2403sp4.x86_64.rpm","bind-libs-9.20.21-4.oe2403sp4.x86_64.rpm","bind-utils-9.20.21-4.oe2403sp4.x86_64.rpm"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3290"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-10723"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-10822"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11331"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11605"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11622"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11721"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12617"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-13204"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-13321"}],"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N"}],"database_specific":{"severity":"High"}}