{"id":"CVE-2026-10822","aliases":["ALPINE-CVE-2026-10822","AZL-93114","BELL-CVE-2026-10822","CLSA-2026-1792648513","DEBIAN-CVE-2026-10822","EUVD-2026-47705","GHSA-42qr-f5rc-vfw9","MGASA-2026-0331","OESA-2026-3289","OESA-2026-3290","OESA-2026-3291","RHSA-2026:54071","SUSE-SU-2026:3426-1","SUSE-SU-2026:3452-1","UBUNTU-CVE-2026-10822","USN-8648-1","USN-8929-1","openSUSE-SU-2026:11375-1","openSUSE-SU-2026:21489-1"],"status":"published","title":"Key Record using PRIVATEDNS algorithm may lead to unexpected exit","description":"If 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.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00422,"percentile":0.36805,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1284","CWE-617"],"published":"2026-07-22T14:09:57Z","modified":"2026-11-05T05:40:51Z","fixes":[{"ecosystem":"Alpine:v3.22","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"bind","fixed_in":["9.20.26-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"bind","fixed_in":["9.20.26-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"bind9","fixed_in":["1:9.18.49-1~deb12u2"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"bind9","fixed_in":["1:9.20.26-1~deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"bind9","fixed_in":["1:9.20.26-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"bind9","fixed_in":["1:9.18.30-0ubuntu0.20.04.2+esm3"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"bind9","fixed_in":["1:9.18.39-0ubuntu0.22.04.5"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"bind9","fixed_in":["1:9.18.39-0ubuntu0.24.04.6"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"bind9","fixed_in":["1:9.20.24-1ubuntu0.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.22","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.11-r0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.20.9-r0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.16-r0"},{"fixed":"9.20.26-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9-dnsutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"bind9utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"dnsutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+tuxcare.els9"}]}],"bundled":13},{"source":"osv","ecosystem":"Debian:12","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.49-1~deb12u2"}]}],"versions":["1:9.18.12-1","1:9.18.13-1","1:9.18.16-1","1:9.18.16-1~deb12u1","1:9.18.16-1~deb12u1~bpo11+1","1:9.18.19-1~deb12u1","1:9.18.19-1~deb12u1~bpo11+1","1:9.18.24-1","1:9.18.24-1~bpo11+1","1:9.18.28-1~deb12u1","1:9.18.28-1~deb12u2","1:9.18.33-1~deb12u2","1:9.18.41-1~deb12u1","1:9.18.44-1~deb12u1","1:9.18.47-1~deb12u1","1:9.18.49-1~deb12u1"]},{"source":"osv","ecosystem":"Debian:13","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.26-1~deb13u1"}]}],"versions":["1:9.20.11-4","1:9.20.15-1","1:9.20.15-1~deb13u1","1:9.20.15-1~deb13u1~bpo12+1","1:9.20.15-2","1:9.20.18-1","1:9.20.18-1~deb13u1","1:9.20.18-1~deb13u1~bpo12+1","1:9.20.19-1","1:9.20.19-1~bpo12+1","1:9.20.20-1","1:9.20.20-1~bpo12+1","1:9.20.21-1","1:9.20.21-1~deb13u1","1:9.20.21-1~deb13u1~bpo12+1","1:9.20.22-1","1:9.20.23-1","1:9.20.23-1~deb13u1","1:9.20.23-1~deb13u1~bpo12+1","1:9.20.24-1","1:9.20.26-1~deb13u1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.26-1"}]}],"versions":["1:9.20.11-4","1:9.20.15-1","1:9.20.15-1~deb13u1","1:9.20.15-1~deb13u1~bpo12+1","1:9.20.15-2","1:9.20.18-1","1:9.20.18-1~deb13u1","1:9.20.18-1~deb13u1~bpo12+1","1:9.20.19-1","1:9.20.19-1~bpo12+1","1:9.20.20-1","1:9.20.20-1~bpo12+1","1:9.20.21-1","1:9.20.21-1~deb13u1","1:9.20.21-1~deb13u1~bpo12+1","1:9.20.22-1","1:9.20.23-1","1:9.20.23-1~deb13u1","1:9.20.23-1~deb13u1~bpo12+1","1:9.20.24-1","1:9.20.26-1~deb13u1","1:9.20.26-1~deb13u1~bpo12+1"]},{"source":"osv","ecosystem":"Mageia:10","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-1.mga10"}]}],"bundled":8},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.21-11.oe2403sp3"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.21-4.oe2403sp4"}]}],"bundled":9},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.21-11.oe2403sp1"}]}],"bundled":7},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-chroot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-dnssec-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.26-0.1.hum1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-150700.3.29.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-150700.3.29.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.50-150600.3.32.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.50-150600.3.32.1"}]}],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"isc-dhcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.3.5-3ubuntu2","4.3.5-3ubuntu3","4.3.5-3ubuntu4","4.3.5-3ubuntu5","4.3.5-3ubuntu6","4.3.5-3ubuntu7","4.3.5-3ubuntu7.1","4.3.5-3ubuntu7.2","4.3.5-3ubuntu7.3","4.3.5-3ubuntu7.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+esm3"}]}],"versions":["1:9.11.5.P4+dfsg-5.1ubuntu2","1:9.11.5.P4+dfsg-5.1ubuntu3","1:9.11.5.P4+dfsg-5.1ubuntu4","1:9.11.5.P4+dfsg-5.1ubuntu5","1:9.11.14+dfsg-1ubuntu1","1:9.11.14+dfsg-3ubuntu1","1:9.16.0-1ubuntu3","1:9.16.0-1ubuntu4","1:9.16.0-1ubuntu5","1:9.16.1-0ubuntu1","1:9.16.1-0ubuntu2","1:9.16.1-0ubuntu2.1","1:9.16.1-0ubuntu2.2","1:9.16.1-0ubuntu2.3","1:9.16.1-0ubuntu2.4","1:9.16.1-0ubuntu2.6","1:9.16.1-0ubuntu2.7","1:9.16.1-0ubuntu2.8","1:9.16.1-0ubuntu2.9","1:9.16.1-0ubuntu2.10","1:9.16.1-0ubuntu2.11","1:9.16.1-0ubuntu2.12","1:9.16.1-0ubuntu2.14","1:9.16.1-0ubuntu2.15","1:9.16.1-0ubuntu2.16","1:9.16.48-0ubuntu0.20.04.1","1:9.18.28-0ubuntu0.20.04.1","1:9.18.30-0ubuntu0.20.04.1","1:9.18.30-0ubuntu0.20.04.2","1:9.18.30-0ubuntu0.20.04.2+esm1","1:9.18.30-0ubuntu0.20.04.2+esm2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"bind9-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:9.11.16+dfsg-3~build1","1:9.11.16+dfsg-3~ubuntu1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.22.04.5"}]}],"versions":["1:9.16.15-1ubuntu1","1:9.16.15-1ubuntu2","1:9.16.15-1ubuntu3","1:9.18.0-2ubuntu1","1:9.18.0-2ubuntu2","1:9.18.0-2ubuntu3","1:9.18.1-1ubuntu1","1:9.18.1-1ubuntu1.1","1:9.18.1-1ubuntu1.2","1:9.18.1-1ubuntu1.3","1:9.18.12-0ubuntu0.22.04.1","1:9.18.12-0ubuntu0.22.04.2","1:9.18.12-0ubuntu0.22.04.3","1:9.18.18-0ubuntu0.22.04.1","1:9.18.18-0ubuntu0.22.04.2","1:9.18.24-0ubuntu0.22.04.1","1:9.18.28-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.1","1:9.18.39-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.3","1:9.18.39-0ubuntu0.22.04.4"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"bind9-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:9.11.19+dfsg-2.1ubuntu1","1:9.11.19+dfsg-2.1ubuntu2","1:9.11.19+dfsg-2.1ubuntu3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.24.04.6"}]}],"versions":["1:9.18.18-0ubuntu2","1:9.18.21-0ubuntu1","1:9.18.24-0ubuntu3","1:9.18.24-0ubuntu4","1:9.18.24-0ubuntu5","1:9.18.28-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.1","1:9.18.39-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.3","1:9.18.39-0ubuntu0.24.04.5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"isc-dhcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.3-P1-2ubuntu5","4.4.3-P1-4ubuntu1","4.4.3-P1-4ubuntu2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu0.2"}]}],"versions":["1:9.20.11-1ubuntu2","1:9.20.11-1ubuntu3","1:9.20.18-1ubuntu1","1:9.20.18-1ubuntu2","1:9.20.18-1ubuntu2.1","1:9.20.24-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"isc-dhcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.3-P1-4ubuntu2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.22.04.5"}]}],"versions":["1:9.16.15-1ubuntu1","1:9.16.15-1ubuntu2","1:9.16.15-1ubuntu3","1:9.18.0-2ubuntu1","1:9.18.0-2ubuntu2","1:9.18.0-2ubuntu3","1:9.18.1-1ubuntu1","1:9.18.1-1ubuntu1.1","1:9.18.1-1ubuntu1.2","1:9.18.1-1ubuntu1.3","1:9.18.12-0ubuntu0.22.04.1","1:9.18.12-0ubuntu0.22.04.2","1:9.18.12-0ubuntu0.22.04.3","1:9.18.18-0ubuntu0.22.04.1","1:9.18.18-0ubuntu0.22.04.2","1:9.18.24-0ubuntu0.22.04.1","1:9.18.28-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.1","1:9.18.39-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.3","1:9.18.39-0ubuntu0.22.04.4"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.24.04.6"}]}],"versions":["1:9.18.18-0ubuntu2","1:9.18.21-0ubuntu1","1:9.18.24-0ubuntu3","1:9.18.24-0ubuntu4","1:9.18.24-0ubuntu5","1:9.18.28-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.1","1:9.18.39-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.3","1:9.18.39-0ubuntu0.24.04.5"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu0.2"}]}],"versions":["1:9.20.11-1ubuntu2","1:9.20.11-1ubuntu3","1:9.20.18-1ubuntu1","1:9.20.18-1ubuntu2","1:9.20.18-1ubuntu2.1","1:9.20.24-1ubuntu0.1"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.9.5.dfsg-3ubuntu0.19+esm15"}]}],"versions":["1:9.9.3.dfsg.P2-4ubuntu1","1:9.9.3.dfsg.P2-4ubuntu2","1:9.9.3.dfsg.P2-4ubuntu3","1:9.9.5.dfsg-2","1:9.9.5.dfsg-3","1:9.9.5.dfsg-3ubuntu0.1","1:9.9.5.dfsg-3ubuntu0.2","1:9.9.5.dfsg-3ubuntu0.3","1:9.9.5.dfsg-3ubuntu0.4","1:9.9.5.dfsg-3ubuntu0.5","1:9.9.5.dfsg-3ubuntu0.6","1:9.9.5.dfsg-3ubuntu0.7","1:9.9.5.dfsg-3ubuntu0.8","1:9.9.5.dfsg-3ubuntu0.9","1:9.9.5.dfsg-3ubuntu0.10","1:9.9.5.dfsg-3ubuntu0.11","1:9.9.5.dfsg-3ubuntu0.12","1:9.9.5.dfsg-3ubuntu0.13","1:9.9.5.dfsg-3ubuntu0.14","1:9.9.5.dfsg-3ubuntu0.15","1:9.9.5.dfsg-3ubuntu0.16","1:9.9.5.dfsg-3ubuntu0.17","1:9.9.5.dfsg-3ubuntu0.18","1:9.9.5.dfsg-3ubuntu0.19","1:9.9.5.dfsg-3ubuntu0.19+esm1","1:9.9.5.dfsg-3ubuntu0.19+esm2","1:9.9.5.dfsg-3ubuntu0.19+esm3","1:9.9.5.dfsg-3ubuntu0.19+esm4","1:9.9.5.dfsg-3ubuntu0.19+esm5","1:9.9.5.dfsg-3ubuntu0.19+esm6","1:9.9.5.dfsg-3ubuntu0.19+esm7","1:9.9.5.dfsg-3ubuntu0.19+esm9","1:9.9.5.dfsg-3ubuntu0.19+esm10","1:9.9.5.dfsg-3ubuntu0.19+esm11","1:9.9.5.dfsg-3ubuntu0.19+esm12","1:9.9.5.dfsg-3ubuntu0.19+esm13","1:9.9.5.dfsg-3ubuntu0.19+esm14"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.10.3.dfsg.P4-8ubuntu1.19+esm11"}]}],"versions":["1:9.9.5.dfsg-11ubuntu1","1:9.9.5.dfsg-12","1:9.9.5.dfsg-12.1","1:9.9.5.dfsg-12.1ubuntu1","1:9.10.3.dfsg.P2-4","1:9.10.3.dfsg.P2-5","1:9.10.3.dfsg.P4-3","1:9.10.3.dfsg.P4-4","1:9.10.3.dfsg.P4-5","1:9.10.3.dfsg.P4-8","1:9.10.3.dfsg.P4-8ubuntu1","1:9.10.3.dfsg.P4-8ubuntu1.1","1:9.10.3.dfsg.P4-8ubuntu1.2","1:9.10.3.dfsg.P4-8ubuntu1.3","1:9.10.3.dfsg.P4-8ubuntu1.4","1:9.10.3.dfsg.P4-8ubuntu1.5","1:9.10.3.dfsg.P4-8ubuntu1.6","1:9.10.3.dfsg.P4-8ubuntu1.7","1:9.10.3.dfsg.P4-8ubuntu1.8","1:9.10.3.dfsg.P4-8ubuntu1.9","1:9.10.3.dfsg.P4-8ubuntu1.10","1:9.10.3.dfsg.P4-8ubuntu1.11","1:9.10.3.dfsg.P4-8ubuntu1.12","1:9.10.3.dfsg.P4-8ubuntu1.14","1:9.10.3.dfsg.P4-8ubuntu1.15","1:9.10.3.dfsg.P4-8ubuntu1.16","1:9.10.3.dfsg.P4-8ubuntu1.17","1:9.10.3.dfsg.P4-8ubuntu1.18","1:9.10.3.dfsg.P4-8ubuntu1.19","1:9.10.3.dfsg.P4-8ubuntu1.19+esm1","1:9.10.3.dfsg.P4-8ubuntu1.19+esm2","1:9.10.3.dfsg.P4-8ubuntu1.19+esm3","1:9.10.3.dfsg.P4-8ubuntu1.19+esm5","1:9.10.3.dfsg.P4-8ubuntu1.19+esm6","1:9.10.3.dfsg.P4-8ubuntu1.19+esm7","1:9.10.3.dfsg.P4-8ubuntu1.19+esm8","1:9.10.3.dfsg.P4-8ubuntu1.19+esm9","1:9.10.3.dfsg.P4-8ubuntu1.19+esm10"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.11.3+dfsg-1ubuntu1.19+esm6"}]}],"versions":["1:9.10.3.dfsg.P4-12.6ubuntu1","1:9.11.2.P1-1ubuntu2","1:9.11.2.P1-1ubuntu3","1:9.11.2.P1-1ubuntu4","1:9.11.2.P1-1ubuntu5","1:9.11.3+dfsg-1ubuntu1","1:9.11.3+dfsg-1ubuntu1.1","1:9.11.3+dfsg-1ubuntu1.2","1:9.11.3+dfsg-1ubuntu1.3","1:9.11.3+dfsg-1ubuntu1.5","1:9.11.3+dfsg-1ubuntu1.7","1:9.11.3+dfsg-1ubuntu1.8","1:9.11.3+dfsg-1ubuntu1.9","1:9.11.3+dfsg-1ubuntu1.10","1:9.11.3+dfsg-1ubuntu1.11","1:9.11.3+dfsg-1ubuntu1.12","1:9.11.3+dfsg-1ubuntu1.13","1:9.11.3+dfsg-1ubuntu1.14","1:9.11.3+dfsg-1ubuntu1.15","1:9.11.3+dfsg-1ubuntu1.16","1:9.11.3+dfsg-1ubuntu1.17","1:9.11.3+dfsg-1ubuntu1.18","1:9.11.3+dfsg-1ubuntu1.19+esm1","1:9.11.3+dfsg-1ubuntu1.19+esm2","1:9.11.3+dfsg-1ubuntu1.19+esm3","1:9.11.3+dfsg-1ubuntu1.19+esm4","1:9.11.3+dfsg-1ubuntu1.19+esm5"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.30-0ubuntu0.20.04.2+esm3"}]}],"versions":["1:9.11.5.P4+dfsg-5.1ubuntu2","1:9.11.5.P4+dfsg-5.1ubuntu3","1:9.11.5.P4+dfsg-5.1ubuntu4","1:9.11.5.P4+dfsg-5.1ubuntu5","1:9.11.14+dfsg-1ubuntu1","1:9.11.14+dfsg-3ubuntu1","1:9.16.0-1ubuntu3","1:9.16.0-1ubuntu4","1:9.16.0-1ubuntu5","1:9.16.1-0ubuntu1","1:9.16.1-0ubuntu2","1:9.16.1-0ubuntu2.1","1:9.16.1-0ubuntu2.2","1:9.16.1-0ubuntu2.3","1:9.16.1-0ubuntu2.4","1:9.16.1-0ubuntu2.6","1:9.16.1-0ubuntu2.7","1:9.16.1-0ubuntu2.8","1:9.16.1-0ubuntu2.9","1:9.16.1-0ubuntu2.10","1:9.16.1-0ubuntu2.11","1:9.16.1-0ubuntu2.12","1:9.16.1-0ubuntu2.14","1:9.16.1-0ubuntu2.15","1:9.16.1-0ubuntu2.16","1:9.16.48-0ubuntu0.20.04.1","1:9.18.28-0ubuntu0.20.04.1","1:9.18.30-0ubuntu0.20.04.1","1:9.18.30-0ubuntu0.20.04.2","1:9.18.30-0ubuntu0.20.04.2+esm1","1:9.18.30-0ubuntu0.20.04.2+esm2"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.22.04.7"}]}],"versions":["1:9.16.15-1ubuntu1","1:9.16.15-1ubuntu2","1:9.16.15-1ubuntu3","1:9.18.0-2ubuntu1","1:9.18.0-2ubuntu2","1:9.18.0-2ubuntu3","1:9.18.1-1ubuntu1","1:9.18.1-1ubuntu1.1","1:9.18.1-1ubuntu1.2","1:9.18.1-1ubuntu1.3","1:9.18.12-0ubuntu0.22.04.1","1:9.18.12-0ubuntu0.22.04.2","1:9.18.12-0ubuntu0.22.04.3","1:9.18.18-0ubuntu0.22.04.1","1:9.18.18-0ubuntu0.22.04.2","1:9.18.24-0ubuntu0.22.04.1","1:9.18.28-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.1","1:9.18.30-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.1","1:9.18.39-0ubuntu0.22.04.2","1:9.18.39-0ubuntu0.22.04.3","1:9.18.39-0ubuntu0.22.04.4","1:9.18.39-0ubuntu0.22.04.5","1:9.18.39-0ubuntu0.22.04.6"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.24.04.8"}]}],"versions":["1:9.18.18-0ubuntu2","1:9.18.21-0ubuntu1","1:9.18.24-0ubuntu3","1:9.18.24-0ubuntu4","1:9.18.24-0ubuntu5","1:9.18.28-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.1","1:9.18.30-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.1","1:9.18.39-0ubuntu0.24.04.2","1:9.18.39-0ubuntu0.24.04.3","1:9.18.39-0ubuntu0.24.04.5","1:9.18.39-0ubuntu0.24.04.6","1:9.18.39-0ubuntu0.24.04.7"],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu0.4"}]}],"versions":["1:9.20.11-1ubuntu2","1:9.20.11-1ubuntu3","1:9.20.18-1ubuntu1","1:9.20.18-1ubuntu2","1:9.20.18-1ubuntu2.1","1:9.20.24-1ubuntu0.1","1:9.20.24-1ubuntu0.2","1:9.20.24-1ubuntu0.3"],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-1.1"}]}],"bundled":9},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.26-160000.1.1"}]}],"bundled":9}],"products":[{"vendor":"isc","product":"bind"},{"vendor":"isc","product":"bind 9"}],"references":[{"url":"https://kb.isc.org/docs/cve-2026-10822","tags":["vendor-advisory","Vendor Advisory","advisory","web","report"]},{"url":"https://downloads.isc.org/isc/bind9/9.20.26","tags":["patch","Product","web"]},{"url":"https://downloads.isc.org/isc/bind9/9.21.24","tags":["patch","Product","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-10822","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-42qr-f5rc-vfw9"},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-10822","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-10822","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1792648513.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-8677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-10723","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-13204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19941","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-75029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-78301","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-10822","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0331.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36003","tags":["report"]},{"url":"https://www.openwall.com/lists/oss-security/2026/07/22/8","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-10723","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-11331","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-11605","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-11622","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-11721","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-12617","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-13204","tags":["web"]},{"url":"https://kb.isc.org/docs/cve-2026-13321","tags":["web"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-12617","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-13321","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-11622","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3291","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:54071","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-11721","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-10822","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-10723","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-13204","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-12617","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-11622","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-13321","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-11331","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54071.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504560","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-10723","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504598","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-10822","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2503721","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-11331","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504298","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-11622","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504338","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-11721","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504370","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-12617","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504447","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-13204","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2504166","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-13321","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263426-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1271982","tags":["report"]},{"url":"https://bugzilla.suse.com/1271983","tags":["report"]},{"url":"https://bugzilla.suse.com/1271984","tags":["report"]},{"url":"https://bugzilla.suse.com/1271985","tags":["report"]},{"url":"https://bugzilla.suse.com/1271986","tags":["report"]},{"url":"https://bugzilla.suse.com/1271987","tags":["report"]},{"url":"https://bugzilla.suse.com/1271988","tags":["report"]},{"url":"https://bugzilla.suse.com/1271989","tags":["report"]},{"url":"https://bugzilla.suse.com/1271990","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-10723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-10822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-12617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-13204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-13321","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263452-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-10822","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8648-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8929-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-10723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-11331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-11605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-11622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-11721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-12617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-13321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-8677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-1519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-13204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-75029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-76163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-77119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-77692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-78301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81736","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-10822","title":"Key Record using PRIVATEDNS algorithm may lead to unexpected exit","description":"If 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.","status":"published","published":"2026-07-22T14:09:57.419Z","modified":"2026-07-22T18:53:34.291Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-617","CWE-1284"],"updated_at":"2026-11-02T13:40:12.486331Z"}],"euvd":[{"id":"EUVD-2026-47705","description":"If 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.","status":"published","published":"2026-07-22T14:09:57Z","modified":"2026-07-22T18:53:34Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T18:19:44.868793Z"}],"ghsa":[{"id":"GHSA-42qr-f5rc-vfw9","title":"If BIND encounters a particular invalid data structure in a DNS record, it will accept the...","description":"If 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.","status":"published","published":"2026-07-22T15:31:26Z","modified":"2026-07-22T15:31:33Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-617"],"updated_at":"2026-11-02T15:09:39.270941Z"}],"nvd":[{"id":"CVE-2026-10822","description":"If 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.","status":"published","published":"2026-07-22T15:16:51.33Z","modified":"2026-11-02T17:46:27.55Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"}],"cwes":["CWE-617","CWE-1284"],"updated_at":"2026-11-02T20:51:40.125089Z"}],"osv":[{"id":"ALPINE-CVE-2026-10822","description":"If 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.","status":"published","published":"2026-07-22T15:16:51.33Z","modified":"2026-11-03T09:30:02.880091739Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T09:56:52.729801Z"},{"id":"BELL-CVE-2026-10822","status":"published","published":"2026-07-23T06:03:32.391202Z","modified":"2026-07-30T07:15:07.331827676Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"CVE-2026-10822","description":"If 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.","status":"published","published":"2026-07-22T15:16:51.33Z","modified":"2026-11-04T02:47:21.922702089Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-04T02:53:45.692342Z"},{"id":"DEBIAN-CVE-2026-10822","description":"If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.  BIND 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. 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.","status":"published","published":"2026-07-22T15:16:51.33Z","modified":"2026-11-03T09:47:41.242558776Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T10:27:58.933618Z"},{"id":"OESA-2026-3289","title":"bind security update","description":"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\nIt is possible for an attacker\u0026apos;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\u0026apos;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 \u0026quot;Next Domain Name\u0026quot; field points outside the signer\u0026apos;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)","status":"published","published":"2026-08-07T02:44:17Z","modified":"2026-08-07T03:00:56.42179036Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:52:46.823443Z"},{"id":"OESA-2026-3290","title":"bind security update","description":"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\u0026apos;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\u0026apos;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 \u0026quot;Next Domain Name\u0026quot; field points outside the signer\u0026apos;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)","status":"published","published":"2026-08-07T02:44:23Z","modified":"2026-08-07T03:00:56.735017697Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:52:46.823443Z"},{"id":"OESA-2026-3291","title":"bind security update","description":"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\nIt is possible for an attacker\u0026apos;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\u0026apos;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 \u0026quot;Next Domain Name\u0026quot; field points outside the signer\u0026apos;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)","status":"published","published":"2026-08-07T02:44:28Z","modified":"2026-08-07T03:00:56.416719235Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:52:46.823443Z"},{"id":"RHSA-2026:54071","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update","status":"published","published":"2026-08-12T10:16:43Z","modified":"2026-10-17T10:15:40Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:21.457353Z"},{"id":"UBUNTU-CVE-2026-10822","description":"If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND 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. 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.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.","status":"published","published":"2026-07-22T15:16:00Z","modified":"2026-10-17T13:11:54.29934348Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:55:59.130573Z"},{"id":"AZL-93114","title":"CVE-2026-10822 affecting package bind for versions less than 9.20.26-1","description":"If 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.","status":"published","published":"2026-07-22T15:16:51Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:25.880689Z"},{"id":"CLSA-2026-1792648513","title":"Fix of 13 CVEs","description":"   * SECURITY UPDATE: CPU exhaustion via malformed DNSKEY records\n     - debian/patches/CVE-2025-8677.patch: fail validation on invalid DNSKEY\n       in lib/dns/validator.c.\n     - CVE-2025-8677\n   * SECURITY UPDATE: cache poisoning through forged records in answers\n     - debian/patches/CVE-2025-40778.patch: tighten resolver caching rules\n       in lib/dns/resolver.c and lib/dns/message.c, and raise the default\n       max-recursion-queries from 32 to 50 in bin/named/config.c.\n     - CVE-2025-40778\n   * SECURITY UPDATE: assertion failure on malformed PRIVATEDNS DNSKEY records\n     - debian/patches/CVE-2026-10822.patch: make dns_name_fromwire() honour\n       the active region of the source buffer in lib/dns/name.c.\n     - CVE-2026-10822\n   * SECURITY UPDATE: crash from malformed NSEC/NSEC3 response\n     - debian/patches/CVE-2026-13204.patch: treat a missing NOQNAME proof as\n       an error instead of an assertion failure in lib/dns/rbtdb.c,\n       lib/dns/resolver.c and lib/ns/query.c.\n     - CVE-2026-13204\n   * SECURITY UPDATE: forged DNSSEC-validated NXDOMAIN responses\n     - debian/patches/CVE-2026-19941.patch: require NSEC wildcard proofs to\n       be signed by the same zone as the NOQNAME proof in\n       lib/dns/validator.c and lib/dns/include/dns/validator.h.\n     - CVE-2026-19941\n   * SECURITY UPDATE: DNSSEC validation bypass via NSEC3 impersonation\n     - debian/patches/CVE-2026-10723.patch: check that the NSEC3 signer\n       matches the owning zone in lib/dns/dnssec.c and lib/isc/result.c.\n     - CVE-2026-10723\n   * SECURITY UPDATE: excessive CPU use validating crafted DNSSEC responses\n     - debian/patches/CVE-2026-19668.patch: bound the DS-to-DNSKEY matching\n       during DNSSEC validation and make the exhausted quota terminal in\n       lib/dns/validator.c and lib/dns/resolver.c.\n     - CVE-2026-19668\n   * SECURITY UPDATE: use-after-free of cached NOQNAME proofs\n     - debian/patches/CVE-2026-19662.patch: keep the cache slabheader that\n       owns a NOQNAME or closest-encloser proof referenced while the proof\n       rdatasets are in use in lib/dns/rbtdb.c.\n     - CVE-2026-19662\n   * SECURITY UPDATE: out-of-zone data above the apex treated as a zone cut\n     - debian/patches/CVE-2026-78301.patch: ignore nodes above the zone\n       origin in RBT zone database lookups in lib/dns/rbtdb.c.\n     - CVE-2026-78301\n   * SECURITY UPDATE: sparsely signed incoming zone transfers accepted\n     - debian/patches/CVE-2026-19033.patch: require a TSIG on every message\n       of an incoming zone transfer in lib/dns/xfrin.c.\n     - CVE-2026-19033\n   * SECURITY UPDATE: memory amplification via duplicate singleton records\n     - debian/patches/CVE-2026-75029.patch: skip duplicate singleton\n       records when parsing DNS messages in lib/dns/message.c.\n     - CVE-2026-75029\n   * SECURITY UPDATE: DNSSEC downgrade of secure delegations via NSEC3\n     from an unrelated sibling zone\n     - debian/patches/CVE-2026-77119.patch: ignore NSEC3 records whose owner\n       zone does not enclose the DS name in the insecure delegation proof\n       in lib/dns/validator.c.\n     - CVE-2026-77119\n   * SECURITY UPDATE: invalid signed wildcard records accepted\n     - debian/patches/CVE-2026-11721.patch: reject RRSIG records whose labels\n       field is lower than the signer label count when parsing and\n       verifying in lib/dns/rdata/generic/rrsig_46.c and lib/dns/dnssec.c,\n       and do not sign out-of-zone records in bin/dnssec/dnssec-signzone.c.\n     - CVE-2026-11721","status":"published","published":"2026-10-22T05:55:37Z","modified":"2026-10-26T09:43:52.034100877Z","updated_at":"2026-11-02T15:43:54.672859Z"},{"id":"MGASA-2026-0331","title":"Updated bind packages fix security vulnerabilities","description":"Updated bind packages fix security vulnerabilities:\nIncorrect acceptance of NSEC3 records. (CVE-2026-10723)\nKey Record using PRIVATEDNS algorithm may lead to unexpected exit.\n(CVE-2026-10822)\nPotential wildcard CNAME RPZ policy bypass. (CVE-2026-11331)\nUnnecessary validation of DNSSEC signed records. (CVE-2026-11605)\nCache poisoning possible with label count discrepancy, RRSIG, and\nwildcards. (CVE-2026-11721)\nRecord ordering based unexpected exit with CNAME or DNAME.\n(CVE-2026-12617)\nUnexpected exit in certain situations with NSEC and NSEC3 both present.\n(CVE-2026-13204)\nDNSSEC Validation Bypass via Out-of-Zone NSEC Next Field.\n(CVE-2026-13321)\n","status":"published","published":"2026-08-10T19:29:27Z","modified":"2026-08-15T18:00:03.56169967Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2026:11375-1","title":"bind-9.20.26-1.1 on GA media","description":"These are all security issues fixed in the bind-9.20.26-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-07-26T00:00:00Z","modified":"2026-07-27T09:00:09.887122119Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:21489-1","title":"Security update for bind","description":"This update for bind fixes the following issues\n\n- Upgrade to release 9.20.26\n- CVE-2026-10723: Incorrect acceptance of NSEC3 records (bsc#1271982).\n- CVE-2026-10822: Key Record using PRIVATEDNS algorithm may lead to unexpected exit (bsc#1271983).\n- CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass (bsc#1271984).\n- CVE-2026-11605: Unnecessary validation of DNSSEC signed records (bsc#1271985).\n- CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).\n- CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).\n- CVE-2026-12617: Record ordering based unexpected exit with CNAME or DNAME (bsc#1271988).\n- CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).\n- CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).\n","status":"published","published":"2026-07-30T10:43:08Z","modified":"2026-07-31T18:24:10.645481001Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"SUSE-SU-2026:3426-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\nUpgrade to release 9.20.26.\n\nSecurity issues fixed:\n\n- CVE-2026-10723: incorrect acceptance of NSEC3 records (bsc#1271982).\n- CVE-2026-10822: key record using PRIVATEDNS algorithm may lead to unexpected exit (bsc#1271983).\n- CVE-2026-11331: potential wildcard CNAME RPZ policy bypass (bsc#1271984).\n- CVE-2026-11605: unnecessary validation of DNSSEC signed records (bsc#1271985).\n- CVE-2026-11622: potential memory usage beyond configured limits (bsc#1271986).\n- CVE-2026-11721: cache poisoning possible with label count discrepancy, RRSIG, and wildcards (bsc#1271987).\n- CVE-2026-12617: record ordering based unexpected exit with CNAME or DNAME (bsc#1271988).\n- CVE-2026-13204: unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).\n- CVE-2026-13321: DNSSEC validation bypass via out-of-zone NSEC Next field (bsc#1271990).\n\nOther updates and bugfixes:\n\n- Release 9.20.26:\n  * Reclaim memory promptly when DNSSEC validations are canceled.\n  * Removed Features:\n    * Remove the secondary validator in query.c.\n    * Remove ineffective TCP fallback after repeated UDP timeouts.\n  * Feature Changes:\n    * Fall back to TCP on receipt of a UDP response with a mismatched\n      query ID.\n    * Limit the number of glue records cached from a referral.\n    * Fix a resolver stall on a CNAME response to a DS query.\n  * Bug Fixes:\n    * Fix a bug in DNS UPDATE processing with inline-signing enabled.\n    * Properly detect private records before copying.\n    * Tighten referral DS acceptance.\n    * Don't synthesize negative responses with pending NSEC.\n    * Check that an NSEC signer is at or above the name to be\n      validated.\n    * Don't evict DNSSEC-validated cache data on a CD=1 NXDOMAIN.\n    * Fix a deny-answer-aliases configuration bypass issue.\n    * Reject external referrals from forwarders.\n    * Fix a zone transfer over TLS (XoT) issue when using the\n      opportunistic TLS mode.\n    * Unvalidated opt-out NSEC3 could be accepted in insecurity\n      proof.\n    * Check wildcard signer and NOQNAME signer match.\n    * Fix CNAME resolution failure caused by a cached SERVFAIL\n      response.\n    * Reject unsupported RSA DNSKEY shapes during DNSSEC validation.\n    * Fix a bug in GeoIP2 string matching.\n    * Fix DNS-over-HTTPS (DoH) quota configuration issue.\n    * Truncated reply to a TSIG query no longer stalls the resolver.\n    * Ignore updates removing DNSKEY RRset with class ANY.\n    * Ignore 0-byte reads in the TCP read callback.\n    * Only print per-zone glue stats when zone-statistics is set to\n      full.\n    * CDS/CDNSKEY records were not removed when re-configuring the\n      server.\n    * Fix a crash when querying an empty non-terminal in a wildcard\n      zone in RBTDB.\n    * Stop reusing outgoing TCP connections the peer has already\n      closed.\n    * Fix DNSSEC validation failures for names under an apex DNAME.\n      * The resolver now removes other RRsets at the same name when\n        caching a CNAME.\n    * Fix nxdomain-redirect combined with dns64.\n    * Fix DNS64 owner case after DNAME restart.\n    * Clear REDIRECT flag when it isn't needed.\n    * Disable output escaping in bind9.xsl.\n    * Fix crash on badly configured secondary signer.\n    * Fix a possible crash on concurrent TKEY DELETE for the same\n      key.\n    * Reject RRSIG records covering meta-types.\n","status":"published","published":"2026-07-30T11:12:12Z","modified":"2026-07-31T09:15:07.882845988Z","updated_at":"2026-11-02T15:54:04.987808Z"},{"id":"SUSE-SU-2026:3452-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-10723: accepting incorrect child-zone NSEC3 records as valid can allow an attacker to forge authenticated\n  NXDOMAIN responses for sibling zones (bsc#1271982).\n- CVE-2026-10822: storing a DNS key record with an invalid PRIVATEDNS algorithm identifier length can trigger a\n  consistency check failure (bsc#1271983).\n- CVE-2026-11331: handling NAMETOOLONG error conditions incorrectly during RPZ wildcard CNAME processing can allow\n  bypassing RPZ rules or triggering process exits (bsc#1271984).\n- CVE-2026-11622: DNSSEC validating resolver under a random subdomain attack can suffer from runaway memory usage\n  exceeding max-cache-size and affecting response rate (bsc#1271986).\n- CVE-2026-11721: RRSIG with fewer labels than its containing zone when synth-from-dnssec is enabled can lead to\n  wildcard generation (bsc#1271987).\n- CVE-2026-12617: delayed or specific CNAME/DNAME query responses combined with positive A record responses can trigger\n  an assertion failure (bsc#1271988).\n- CVE-2026-13204: validating a domain covered by both NSEC and NSEC3 with an RRSIG for only one type can trigger an\n  assertion failure (bsc#1271989).\n- CVE-2026-13321: NSEC records with a `Next Domain Name` pointing outside the signer's zone can allow cross-zone cache\n  poisoning and authenticated denial-of-service responses (bsc#1271990).\n\n- Update to release 9.18.50:\n\n * Remove ineffective TCP fallback after repeated UDP timeouts.\n * Fall back to TCP on receipt of a UDP response with a mismatched query ID.\n * Fix DNS64 owner case after DNAME restart.\n * Clear REDIRECT flag when it isn't needed.\n","status":"published","published":"2026-08-03T11:34:55Z","modified":"2026-08-04T11:45:06.336072676Z","updated_at":"2026-11-02T15:54:04.987808Z"},{"id":"USN-8648-1","title":"bind9 vulnerabilities","description":"It was discovered that Bind incorrectly accepted NSEC3 records whose signer\nname did not match the owning zone. A remote attacker could possibly use\nthis issue to perform NSEC3 impersonation attacks, bypassing DNSSEC\nvalidation. (CVE-2026-10723)\n\nIt was discovered that Bind incorrectly handled Key Records using the\nPRIVATEDNS algorithm. A remote attacker could possibly use this issue to\ncause Bind to crash, resulting in a denial of service. (CVE-2026-10822)\n\nIt was discovered that Bind incorrectly handled wildcard CNAME expansion in\nResponse Policy Zones. A remote attacker could possibly use this issue to\nbypass configured RPZ policies. (CVE-2026-11331)\n\nIt was discovered that Bind performed unnecessary validation of DNSSEC\nsigned records. A remote attacker could possibly use this issue to cause\nBind to use excessive resources, leading to a denial of service. This issue\nonly affected Ubuntu 26.04 LTS. (CVE-2026-11605)\n\nIt was discovered that Bind incorrectly tracked memory usage in the DNS\ncache. A remote attacker could possibly use this issue to cause Bind to use\nmemory beyond configured limits, leading to a denial of service.\n(CVE-2026-11622)\n\nIt was discovered that Bind incorrectly handled signed wildcard records\nwith label count discrepancies and RRSIG validation. A remote attacker\ncould possibly use this issue to perform cache poisoning attacks.\n(CVE-2026-11721)\n\nIt was discovered that Bind incorrectly handled certain CNAME and DNAME\nrecord orderings in the resolver. A remote attacker could possibly use this\nissue to cause Bind to crash, resulting in a denial of service.\n(CVE-2026-12617)\n\nIt was discovered that Bind incorrectly validated out-of-zone NSEC next\nowner names during DNSSEC validation. A remote attacker could possibly use\nthis issue to bypass DNSSEC validation. (CVE-2026-13321)","status":"published","published":"2026-08-19T11:45:39Z","modified":"2026-08-19T19:30:09.769643948Z","updated_at":"2026-11-02T16:58:25.103481Z"},{"id":"USN-8929-1","title":"bind9 vulnerabilities","description":"Zuyao Xu and Xiang Li discovered that Bind incorrectly handled certain\nmalformed DNSKEY records. A remote attacker could possibly use this issue\nto cause Bind to consume resources, resulting in a denial of service. This\nissue only affected Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, and Ubuntu 18.04\nLTS. (CVE-2025-8677)\n\nYuxiao Wu, Yunyi Zhang, Baojun Liu, and Haixin Duan discovered that Bind\nincorrectly accepted certain records from answers. A remote attacker could\npossibly use this issue to perform a cache poisoning attack. This issue\nonly affected Ubuntu 18.04 LTS. (CVE-2025-40778)\n\nSamy Medjahed discovered that Bind incorrectly handled insecure delegation\nvalidation. A remote attacker could possibly use this issue to cause\nexcessive NSEC3 iterations, consuming CPU resources, and leading to a\ndenial of service. This issue only affected Ubuntu 14.04 LTS, Ubuntu 16.04\nLTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-1519)\n\nIt was discovered that Bind incorrectly accepted NSEC3 records whose signer\nname did not match the owning zone. A remote attacker could possibly use\nthis issue to perform NSEC3 impersonation attacks, bypassing DNSSEC\nvalidation. This issue only affected Ubuntu 14.04 LTS, Ubuntu 16.04 LTS,\nUbuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2026-10723)\n\nIt was discovered that Bind incorrectly handled Key Records using the\nPRIVATEDNS algorithm. A remote attacker could possibly use this issue to\ncause Bind to crash, resulting in a denial of service. This issue only\naffected Ubuntu 20.04 LTS. (CVE-2026-10822)\n\nIt was discovered that Bind incorrectly handled wildcard CNAME expansion in\nResponse Policy Zones. A remote attacker could possibly use this issue to\nbypass configured RPZ policies. This issue only affected Ubuntu 20.04 LTS.\n(CVE-2026-11331)\n\nIt was discovered that Bind incorrectly tracked memory usage in the DNS\ncache. A remote attacker could possibly use this issue to cause Bind to use\nmemory beyond configured limits, leading to a denial of service. This issue\nonly affected Ubuntu 20.04 LTS. (CVE-2026-11622)\n\nIt was discovered that Bind incorrectly handled signed wildcard records\nwith label count discrepancies and RRSIG validation. A remote attacker\ncould possibly use this issue to perform cache poisoning attacks. This\nissue only affected Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS,\nand Ubuntu 20.04 LTS. (CVE-2026-11721)\n\nIt was discovered that Bind incorrectly handled DNSSEC validation when a\ndomain was covered by both NSEC and NSEC3 records with only one type having\nan RRSIG. A remote attacker could possibly use this issue to cause Bind to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.\n(CVE-2026-13204)\n\nIt was discovered that Bind incorrectly validated out-of-zone NSEC next\nowner names during DNSSEC validation. A remote attacker could possibly use\nthis issue to bypass DNSSEC validation. This issue only affected Ubuntu\n14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.\n(CVE-2026-13321)\n\nIt was discovered that Bind incorrectly served zone transfer data before\nverifying the TSIG signature on multi-message transfers. A remote attacker\ncould possibly use this issue to send unauthorized zone contents to a\nsecondary server. (CVE-2026-19033)\n\nIt was discovered that Bind incorrectly handled the lifetime of cached\nDNSSEC proofs, leading to a use-after-free. A remote attacker could\npossibly use this issue to cause Bind to crash, resulting in a denial of\nservice. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS,\nUbuntu 24.04 LTS, and Ubuntu 26.04 LTS. (CVE-2026-19662)\n\nIt was discovered that Bind incorrectly handled certain malformed answers\nwhen configured to use DNS64. A remote attacker could possibly use this\nissue to cause Bind to crash, resulting in a denial of service.\n(CVE-2026-19666)\n\nIt was discovered that Bind incorrectly handled oversized negative answers\nwhen storing them in the negative cache. A remote attacker could possibly\nuse this issue to cause Bind to crash, resulting in a denial of service.\nThis issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04\nLTS, and Ubuntu 26.04 LTS. (CVE-2026-19667)\n\nIt was discovered that Bind incorrectly handled large numbers of certain\ninvalid DNSSEC records during validation. A remote attacker could possibly\nuse this issue to cause Bind to use excessive resources, leading to a\ndenial of service. This issue only affected Ubuntu 26.04 LTS.\n(CVE-2026-19668)\n\nIt was discovered that Bind incorrectly accepted inapplicable NSEC records\nas proof that no wildcard existed. A remote attacker could possibly use\nthis issue to forge NXDOMAIN responses, masking the existence of wildcard\nrecords. (CVE-2026-19941)\n\nIt was discovered that Bind incorrectly handled repeated copies of records\nthat should only appear once, such as SOA, CNAME, or DNAME records. A\nremote attacker could possibly use this issue to cause Bind to use\nexcessive memory, leading to a denial of service. (CVE-2026-75029)\n\nIt was discovered that Bind incorrectly handled TKEY queries when the\nconfiguration did not contain a global options block. A remote attacker\ncould possibly use this issue to cause Bind to crash, resulting in a denial\nof service. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-76163)\n\nIt was discovered that Bind incorrectly accepted NSEC3 records from\nunrelated sibling zones as proof of an insecure delegation. A remote\nattacker could possibly use this issue to bypass DNSSEC validation and\ninject forged unsigned answers. (CVE-2026-77119)\n\nIt was discovered that Bind incorrectly handled DNS-over-HTTPS requests\ncontaining invalid SIG(0) records when the connection was closed\nprematurely. A remote attacker could possibly use this issue to cause Bind\nto crash, resulting in a denial of service. This issue only affected Ubuntu\n26.04 LTS. (CVE-2026-77692)\n\nIt was discovered that Bind incorrectly treated NS or DNAME records above\nthe zone origin as zone cuts. An attacker could possibly use this issue to\ncause Bind to serve or cache out-of-zone data, resulting in cache\npoisoning. (CVE-2026-78301)\n\nIt was discovered that Bind incorrectly handled wildcard answers with both\nNSEC3 and NSEC proofs at the same owner name. A remote attacker could\npossibly use this issue to cause Bind to crash, resulting in a denial of\nservice. (CVE-2026-80274)\n\nIt was discovered that Bind incorrectly released resources when processing\nSVCB and HTTPS AliasMode records. A remote attacker could possibly use this\nissue to cause Bind to exhaust resources, leading to a denial of service.\nThis issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04\nLTS, and Ubuntu 26.04 LTS. (CVE-2026-81563)\n\nIt was discovered that Bind incorrectly limited additional processing for\ncached SVCB and HTTPS AliasMode records. A remote attacker could possibly\nuse this issue to cause Bind to use excessive CPU resources, leading to a\ndenial of service. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04\nLTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS. (CVE-2026-81736)","status":"published","published":"2026-10-14T13:00:49Z","modified":"2026-10-17T13:11:54.621775565Z","updated_at":"2026-11-02T16:58:26.907654Z"}]}}