{"id":"CVE-2026-19941","aliases":["ALPINE-CVE-2026-19941","AZL-103359","BELL-CVE-2026-19941","CLSA-2026-1792590954","CLSA-2026-1792648513","DEBIAN-CVE-2026-19941","EUVD-2026-80745","GHSA-38fx-cm5x-27pg","MGASA-2026-0422","OESA-2026-4340","OESA-2026-4341","OESA-2026-4342","OESA-2026-4343","RHSA-2026:68279","SUSE-SU-2026:24157-1","SUSE-SU-2026:4285-1","SUSE-SU-2026:4608-1","SUSE-SU-2026:4635-1","SUSE-SU-2026:4664-1","SUSE-SU-2026:4772-1","SUSE-SU-2026:5118-1","UBUNTU-CVE-2026-19941","USN-8929-1","USN-8969-1","openSUSE-SU-2026:11916-1","openSUSE-SU-2026:22049-1"],"status":"published","title":"checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00226,"percentile":0.1339,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-345"],"published":"2026-09-16T13:52:49Z","modified":"2026-11-06T14:16:27Z","fixes":[{"ecosystem":"Alpine:v3.22","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"bind","fixed_in":["9.20.30-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"bind","fixed_in":["9.20.29-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"bind9","fixed_in":["1:9.18.49-1~deb12u3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"bind9","fixed_in":["1:9.20.29-1~deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"bind9","fixed_in":["1:9.20.29-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:14.04:LTS","package":"bind9","fixed_in":["1:9.9.5.dfsg-3ubuntu0.19+esm15"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"bind9","fixed_in":["1:9.10.3.dfsg.P4-8ubuntu1.19+esm11"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"bind9","fixed_in":["1:9.11.3+dfsg-1ubuntu1.19+esm6"],"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.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"bind9","fixed_in":["1:9.18.39-0ubuntu0.24.04.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.10","package":"bind9","fixed_in":["1:9.20.24-1ubuntu3.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"bind9","fixed_in":["1:9.20.24-1ubuntu0.4"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.22","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.30-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.11-r0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.20.9-r0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.18.16-r0"},{"fixed":"9.20.29-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-chroot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-dnssec-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-dnssec-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-license","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bind-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"32:9.16.23-11.el9_2.2.tuxcare.els17"}]}],"bundled":3},{"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~deb12u3"}]}],"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","1:9.18.49-1~deb12u2"]},{"source":"osv","ecosystem":"Debian:13","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.29-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","1:9.20.26-1~deb13u1","1:9.20.26-1~deb13u1~bpo12+1","1:9.20.27-1","1:9.20.27-2"]},{"source":"osv","ecosystem":"Debian:14","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.29-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","1:9.20.26-1~deb13u1","1:9.20.26-1~deb13u1~bpo12+1","1:9.20.27-1","1:9.20.27-2","1:9.20.29-1~deb13u1"]},{"source":"osv","ecosystem":"Mageia:10","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-1.mga10"}]}],"bundled":14},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.21-14.oe2403sp3"}]}],"bundled":5},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.21-7.oe2403sp4"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.23-33.oe2203sp4"}]}],"bundled":5},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.21-14.oe2403sp1"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-chroot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-dnssec-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:hummingbird:1","package":"bind-utils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:9.20.29-0.1.hum1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-160000.1.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-160000.1.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-150700.3.32.2"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-150700.3.32.2"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.18.50-150600.3.35.1"}]}],"bundled":10},{"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.35.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.11.22-3.77.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.11.22-3.77.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150400.5.70.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150400.5.70.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150400.5.70.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150400.5.70.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150500.8.46.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150500.8.46.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150500.8.46.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150500.8.46.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.50-150500.8.46.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Multi Linux Manager Tools SLE-Micro-5","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.16.6-150000.12.97.1"}]}],"bundled":7},{"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"]},{"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"]},{"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"]},{"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.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"]},{"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.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"]},{"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.10","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu3.1"}]}],"versions":["1:9.20.18-1ubuntu2","1:9.20.23-1ubuntu1","1:9.20.24-1ubuntu2","1:9.20.24-1ubuntu3"]},{"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"]},{"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: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":"Ubuntu:22.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.22.04.8"}]}],"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","1:9.18.39-0ubuntu0.22.04.7"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.18.39-0ubuntu0.24.04.9"}]}],"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","1:9.18.39-0ubuntu0.24.04.8"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu3.1"}]}],"versions":["1:9.20.18-1ubuntu2","1:9.20.23-1ubuntu1","1:9.20.24-1ubuntu2","1:9.20.24-1ubuntu3"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"bind9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:9.20.24-1ubuntu0.5"}]}],"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","1:9.20.24-1ubuntu0.4"],"bundled":18},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-1.1"}]}],"bundled":14},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"bind","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.20.29-160000.1.1"}]}],"bundled":14}],"products":[{"vendor":"isc","product":"bind 9"}],"references":[{"url":"https://kb.isc.org/docs/cve-2026-19941","tags":["vendor-advisory","web","article","report"]},{"url":"https://downloads.isc.org/isc/bind9/9.20.29","tags":["patch","article"]},{"url":"https://downloads.isc.org/isc/bind9/9.21.26","tags":["patch","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19941","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-38fx-cm5x-27pg"},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-19941","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-19941","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1792590954.html","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://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-10822","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-78301","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-19941","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0422.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36326","tags":["report"]},{"url":"https://kb.isc.org/docs/cve-2026-19033","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-19662","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-19666","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-19667","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-19668","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-75029","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-76163","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-77119","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-77692","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-78301","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-80274","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-81563","tags":["web","article"]},{"url":"https://kb.isc.org/docs/cve-2026-81736","tags":["web","article"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4340","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4341","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4342","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4343","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:68279","tags":["advisory"]},{"url":"https://images.redhat.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-81736","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-76163","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-78301","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-75029","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-80274","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-81563","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77692","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19666","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19668","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19033","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19662","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19667","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19941","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-77119","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_68279.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535479","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19033","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535445","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19662","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535477","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19666","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19667","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535476","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19668","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535457","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19941","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535468","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-75029","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535467","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-76163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-76163","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535469","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77119","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535462","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77692","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535463","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-78301","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535466","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80274","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535461","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81563","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535432","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81736","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81736","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624157-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1280430","tags":["report"]},{"url":"https://bugzilla.suse.com/1280432","tags":["report"]},{"url":"https://bugzilla.suse.com/1280433","tags":["report"]},{"url":"https://bugzilla.suse.com/1280435","tags":["report"]},{"url":"https://bugzilla.suse.com/1280436","tags":["report"]},{"url":"https://bugzilla.suse.com/1280437","tags":["report"]},{"url":"https://bugzilla.suse.com/1280438","tags":["report"]},{"url":"https://bugzilla.suse.com/1280439","tags":["report"]},{"url":"https://bugzilla.suse.com/1280440","tags":["report"]},{"url":"https://bugzilla.suse.com/1280441","tags":["report"]},{"url":"https://bugzilla.suse.com/1280442","tags":["report"]},{"url":"https://bugzilla.suse.com/1280443","tags":["report"]},{"url":"https://bugzilla.suse.com/1280444","tags":["report"]},{"url":"https://bugzilla.suse.com/1280445","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-75029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-76163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-77119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-77692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-78301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81736","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264285-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264608-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264635-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264664-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264772-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20265118-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-19941","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8929-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8969-1","tags":["advisory"]},{"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-10723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-10822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-11331","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-13204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-13321","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-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":"https://ubuntu.com/security/CVE-2026-19630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-94300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-96888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97313","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-19941","title":"checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T13:52:49.4Z","modified":"2026-09-17T18:44:20.015Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-345"],"updated_at":"2026-11-02T13:47:17.512524Z"}],"euvd":[{"id":"EUVD-2026-80745","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T13:52:49Z","modified":"2026-09-17T18:44:20Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T17:28:10.38936Z"}],"ghsa":[{"id":"GHSA-38fx-cm5x-27pg","title":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard...","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T15:31:10Z","modified":"2026-09-16T15:31:13Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"cwes":["CWE-345"],"updated_at":"2026-11-02T15:11:59.582427Z"}],"nvd":[{"id":"CVE-2026-19941","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T14:17:05.16Z","modified":"2026-10-26T21:10:00.17Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-345"],"updated_at":"2026-11-02T14:12:48.630594Z"}],"osv":[{"id":"ALPINE-CVE-2026-19941","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T14:17:05.16Z","modified":"2026-10-01T02:17:49.199374895Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:27:50.269992Z"},{"id":"BELL-CVE-2026-19941","status":"published","published":"2026-09-18T06:05:43.29694Z","modified":"2026-09-30T07:15:03.688421563Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"DEBIAN-CVE-2026-19941","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. 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.","status":"published","published":"2026-09-16T14:17:05.16Z","modified":"2026-10-28T00:00:28.162348892Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:53.097669Z"},{"id":"OESA-2026-4340","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\nFor a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945.\nThis 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-19033)\n\nAn attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort.\nThis issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.(CVE-2026-19662)\n\nAn inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim\u0026apos;s wildcard record.\nThis 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-19941)\n\nIn a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other memory attack vectors.\nThis 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-75029)\n\nA malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database.\nThis 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-78301)","status":"published","published":"2026-10-16T11:59:32Z","modified":"2026-10-16T12:15:13.595216371Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:47.981622Z"},{"id":"OESA-2026-4341","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\nFor a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945.\nThis 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-19033)\n\nAn attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort.\nThis issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.(CVE-2026-19662)\n\nA BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record.  Default limits on \u0026quot;max-records-per-type\u0026quot; and \u0026quot;max-types-per-name\u0026quot; help mitigate the exposure.\nThis 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-19668)\n\nAn inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim\u0026apos;s wildcard record.\nThis 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-19941)\n\nIn a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other memory attack vectors.\nThis 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-75029)\n\nA 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.\nThis 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)\n\nA malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database.\nThis 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-78301)","status":"published","published":"2026-10-16T11:59:32Z","modified":"2026-10-16T12:15:19.076792519Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:47.981622Z"},{"id":"OESA-2026-4342","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\nFor a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945.\nThis 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-19033)\n\nAn attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort.\nThis issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.(CVE-2026-19662)\n\nAn inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim\u0026apos;s wildcard record.\nThis 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-19941)\n\nIn a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other memory attack vectors.\nThis 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-75029)\n\nA malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database.\nThis 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-78301)","status":"published","published":"2026-10-16T11:59:33Z","modified":"2026-10-16T12:15:19.977380429Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:47.981622Z"},{"id":"OESA-2026-4343","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\nFor a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945.\nThis 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-19033)\n\nAn attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort.\nThis issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.(CVE-2026-19662)\n\nAn inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim\u0026apos;s wildcard record.\nThis 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-19941)\n\nIn a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other memory attack vectors.\nThis 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-75029)\n\nA malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database.\nThis 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-78301)","status":"published","published":"2026-10-16T11:59:34Z","modified":"2026-10-16T12:15:19.46068686Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:47.981622Z"},{"id":"RHSA-2026:68279","title":"Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update","status":"published","published":"2026-09-22T10:19:09Z","modified":"2026-10-17T10:18:30Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:22.406388Z"},{"id":"UBUNTU-CVE-2026-19941","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. 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.","status":"published","published":"2026-09-16T14:17:00Z","modified":"2026-11-03T21:17:34.243356965Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"AZL-103359","title":"CVE-2026-19941 affecting package bind for versions less than 9.20.30-1","description":"An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record.\nThis 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.","status":"published","published":"2026-09-16T14:17:05Z","modified":"2026-11-06T14:16:27.8195324Z","updated_at":"2026-11-06T14:57:15.495576Z"},{"id":"CLSA-2026-1792590954","title":"bind: Fix of 3 CVEs","description":"- CVE-2026-19941: require an NSEC wildcard proof to be signed by the same zone\n  as the validated NOQNAME proof\n- CVE-2026-75029: skip duplicate records of singleton types when parsing\n  a message\n- CVE-2026-77119: ignore NSEC3 records from zones that do not enclose the DS\n  name when proving an insecure referral","status":"published","published":"2026-10-21T22:33:09Z","modified":"2026-10-26T09:31:02.928268853Z","updated_at":"2026-11-02T15:43:54.672859Z"},{"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-0422","title":"Updated bind package fixes security vulnerabilities","description":"Unauthenticated IXFR deltas are applied to the live zone before TSIG\nverification (CVE-2026-19033).\nqpcache NOQNAME proof use-after-free crashes recursive resolver\n(CVE-2026-19662).\nUse-after-free in query_addnoqnameproof() via the DNS64 filter64 path\n(CVE-2026-19666).\nRemote assertion failure via 16-bit length truncation in\ndns_ncache_add() (CVE-2026-19667).\nResource Exhaustion via Excessive DNSSEC Cryptographic Material Matching\n(CVE-2026-19668).\ncheckwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence\nproof (CVE-2026-19941).\nMessage parser retains every identical singleton RDATA, enabling\nwire-to-work amplification (CVE-2026-75029).\nnamed aborts on a TKEY query when the user configuration has no global\noptions statement (CVE-2026-76163).\nNSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets\n(CVE-2026-77119).\nUnauthenticated remote crash of named via a single DoH SIG(0) request\n(CVE-2026-77692).\nOut-of-zone database nodes can become authoritative zone cuts\n(CVE-2026-78301).\nValidating resolver can abort while caching a mismatched NOQNAME proof\n(CVE-2026-80274).\nSVCB AliasMode additional-data error leaks qpcache references\n(CVE-2026-81563).\nRemote CPU denial of service through cached SVCB/HTTPS AliasMode trees\n(CVE-2026-81736).\n","status":"published","published":"2026-09-20T04:25:32Z","modified":"2026-09-20T04:30:03.02064766Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2026:11916-1","title":"bind-9.20.29-1.1 on GA media","description":"These are all security issues fixed in the bind-9.20.29-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-09-29T00:00:00Z","modified":"2026-09-30T18:23:13.922956675Z","updated_at":"2026-11-02T16:58:40.245664Z"},{"id":"openSUSE-SU-2026:22049-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement\n  (bsc#1280439).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request (bsc#1280441).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n- CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).\n- CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).\n\nChanges for bind:\n\n- Upgrade to release 9.20.29\n Feature Changes:\n * Reject oversized and malformed DNSKEY records up front.\n * Speed up RPZ policy zone updates.\n Bug Fixes:\n * Prevent a crash when using both dns64 and filter-a.\n * Stop passing UDP client addresses to update-policy external\n helpers.\n * Missing required NSEC3 for delegation not detected.\n * Tighten EUI48 and EUI64 text parsing.\n * GeoIP ACL state could be stale or wrong after reload.\n * Honor DNSSEC policy key tag ranges.\n * Fix a double free in mdig when EDNS options are specified.\n * Fix a crash when an IXFR falls back to AXFR with updates still\n pending.\n * Fix DS requests to parental agents over TLS.\n * Fix the rndc-confgen -q (quiet) option.\n * Enforce query ACLs for redirect zones and searched DLZs.\n * Check asnum validity in GeoIP ACLs.\n * Fix a crash on remote-servers lists that reference themselves.\n * A record from outside a response policy zone could crash named.\n * Invalid key-store configuration could abort the DNSSEC tools.\n * NSEC signature set could bypass the secure-delegation check.\n * Fix a possible nsupdate issue when using GSS-TSIG.\n * Fix a crash with a single-element geoip sortlist.\n * Prevent out-of-bailiwick CNAMEs from evicting cached records.\n * Restore periodic cleanup of stale resolver address data.\n * Fix named-checkconf/named crash with malformed key name.\n * Prevent resolver crashes while processing DNS over TCP.\n * Ensure NSEC authority does not cross zonecut boundary.\n * Treat an unusable NSEC3 chain as a verification failure.\n * Treat non-canonical RPZ prefixes as any other failure.\n * Negative caching stopped working with\n stale-answer-client-timeout set to 0.\n * An unterminated OpenSSL private-key Label: field could be read\n past its parser buffer.\n * Restore SMF support on Solaris and illumos.\n * Fix compilation on GNU/Hurd.\n * dig +yaml was producing invalid YAML when a lookup failed.\n * Properly prevent TSIG generation command line injection\n attacks.\n * Fix a potential heap bounds overflow write in dnssec-signzone.\n * Fix crashes on invalid DNSTAP input in dnstap-read.\n","status":"published","published":"2026-10-07T09:32:20Z","modified":"2026-10-19T17:23:10.642945355Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:24157-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement\n  (bsc#1280439).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request (bsc#1280441).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n- CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).\n- CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).\n\nChanges for bind:\n\n- Upgrade to release 9.20.29\n Feature Changes:\n * Reject oversized and malformed DNSKEY records up front.\n * Speed up RPZ policy zone updates.\n Bug Fixes:\n * Prevent a crash when using both dns64 and filter-a.\n * Stop passing UDP client addresses to update-policy external\n helpers.\n * Missing required NSEC3 for delegation not detected.\n * Tighten EUI48 and EUI64 text parsing.\n * GeoIP ACL state could be stale or wrong after reload.\n * Honor DNSSEC policy key tag ranges.\n * Fix a double free in mdig when EDNS options are specified.\n * Fix a crash when an IXFR falls back to AXFR with updates still\n pending.\n * Fix DS requests to parental agents over TLS.\n * Fix the rndc-confgen -q (quiet) option.\n * Enforce query ACLs for redirect zones and searched DLZs.\n * Check asnum validity in GeoIP ACLs.\n * Fix a crash on remote-servers lists that reference themselves.\n * A record from outside a response policy zone could crash named.\n * Invalid key-store configuration could abort the DNSSEC tools.\n * NSEC signature set could bypass the secure-delegation check.\n * Fix a possible nsupdate issue when using GSS-TSIG.\n * Fix a crash with a single-element geoip sortlist.\n * Prevent out-of-bailiwick CNAMEs from evicting cached records.\n * Restore periodic cleanup of stale resolver address data.\n * Fix named-checkconf/named crash with malformed key name.\n * Prevent resolver crashes while processing DNS over TCP.\n * Ensure NSEC authority does not cross zonecut boundary.\n * Treat an unusable NSEC3 chain as a verification failure.\n * Treat non-canonical RPZ prefixes as any other failure.\n * Negative caching stopped working with\n stale-answer-client-timeout set to 0.\n * An unterminated OpenSSL private-key Label: field could be read\n past its parser buffer.\n * Restore SMF support on Solaris and illumos.\n * Fix compilation on GNU/Hurd.\n * dig +yaml was producing invalid YAML when a lookup failed.\n * Properly prevent TSIG generation command line injection\n attacks.\n * Fix a potential heap bounds overflow write in dnssec-signzone.\n * Fix crashes on invalid DNSTAP input in dnstap-read.\n","status":"published","published":"2026-10-07T09:32:27Z","modified":"2026-10-16T17:23:11.550202292Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:4285-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement\n  (bsc#1280439).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request (bsc#1280441).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n- CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).\n- CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).\n\nChanges for bind:\n\nUpgrade to release 9.20.29\n  \n New Features:\n * Disclose active Negative Trust Anchors with Extended DNS Error\n 33.\n Feature Changes:\n * Reject oversized and malformed DNSKEY records up front.\n * Speed up RPZ policy zone updates.\n Bug Fixes:\n * Prevent a crash when using both dns64 and filter-a.\n * Stop passing UDP client addresses to update-policy external\n helpers.\n * Missing required NSEC3 for delegation not detected.\n * Tighten EUI48 and EUI64 text parsing.\n * GeoIP ACL state could be stale or wrong after reload.\n * Honor DNSSEC policy key tag ranges.\n * Fix a double free in mdig when EDNS options are specified.\n * Fix a crash when an IXFR falls back to AXFR with updates still\n pending.\n * Fix DS requests to parental agents over TLS.\n * Fix the rndc-confgen -q (quiet) option.\n * Enforce query ACLs for redirect zones and searched DLZs.\n * Check asnum validity in GeoIP ACLs.\n * Fix a crash on remote-servers lists that reference themselves.\n * A record from outside a response policy zone could crash named.\n * Invalid key-store configuration could abort the DNSSEC tools.\n * NSEC signature set could bypass the secure-delegation check.\n * Fix a possible nsupdate issue when using GSS-TSIG.\n * Fix a crash with a single-element geoip sortlist.\n * Prevent out-of-bailiwick CNAMEs from evicting cached records.\n * Restore periodic cleanup of stale resolver address data.\n * Fix named-checkconf/named crash with malformed key name.\n * Prevent resolver crashes while processing DNS over TCP.\n * Ensure NSEC authority does not cross zonecut boundary.\n * Treat an unusable NSEC3 chain as a verification failure.\n * Treat non-canonical RPZ prefixes as any other failure.\n * Negative caching stopped working with\n stale-answer-client-timeout set to 0.\n * An unterminated OpenSSL private-key Label: field could be read\n past its parser buffer.\n * Restore SMF support on Solaris and illumos.\n * Fix compilation on GNU/Hurd.\n * dig +yaml was producing invalid YAML when a lookup failed.\n * Properly prevent TSIG generation command line injection\n attacks.\n * Fix a potential heap bounds overflow write in dnssec-signzone.\n * Fix crashes on invalid DNSTAP input in dnstap-read.\n","status":"published","published":"2026-09-22T16:08:33Z","modified":"2026-09-23T09:15:05.451835744Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:4608-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n- CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).\n- CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).\n","status":"published","published":"2026-10-09T15:54:44Z","modified":"2026-10-10T09:30:06.431763532Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:4635-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n","status":"published","published":"2026-10-13T07:42:52Z","modified":"2026-10-13T17:23:10.181963096Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:4664-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n","status":"published","published":"2026-10-14T12:53:16Z","modified":"2026-10-15T10:30:33.42639486Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:4772-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).\n- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).\n","status":"published","published":"2026-10-20T17:58:10Z","modified":"2026-10-21T13:00:04.827405136Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:5118-1","title":"Security update for bind","description":"This update for bind fixes the following issues:\n\n- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).\n- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).\n- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).\n- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).\n- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification\n  (bsc#1280438).\n- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).\n- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).\n","status":"published","published":"2026-11-05T12:00:35Z","modified":"2026-11-05T19:00:04.177672046Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"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"},{"id":"USN-8969-1","title":"bind9 vulnerabilities","description":"It was discovered that Bind incorrectly handled certain DNS messages\nwith repeated singleton records such as SOA, CNAME, or DNAME records.\nA remote attacker could possibly use this issue to cause Bind to use\nexcessive memory, leading to a denial of service. This issue only affected\nUbuntu 26.10. (CVE-2026-75029)\n\nIt was discovered that Bind incorrectly handled cached DNSSEC proofs.\nA remote attacker could possibly use this issue to cause Bind to crash,\nresulting in a denial of service. This issue only affected\nUbuntu 26.10. (CVE-2026-19662)\n\nIt was discovered that Bind incorrectly handled certain invalid DNSSEC\nrecords. A remote attacker could possibly use this issue to cause Bind\nto use excessive CPU resources, leading to a denial of service. This issue only affected\nUbuntu 26.10.\n(CVE-2026-19668)\n\nIt was discovered that Bind incorrectly handled malformed answers on\nresolvers configured to use DNS64. A remote attacker could possibly use\nthis issue to cause Bind to crash, resulting in a denial of service. This issue only affected\nUbuntu 26.10.\n(CVE-2026-19666)\n\nIt was discovered that Bind incorrectly handled TKEY queries when no\nglobal options block was present. A remote attacker could possibly use\nthis issue to cause Bind to crash, resulting in a denial of service.\nThis issue only affected\nUbuntu 26.10.\n(CVE-2026-76163)\n\nIt was discovered that Bind incorrectly verified TSIG signatures during\nzone transfers. A remote attacker could possibly use this issue to inject\nunauthorized zone contents into a secondary server. This issue only affected\nUbuntu 26.10. (CVE-2026-19033)\n\nIt was discovered that Bind incorrectly handled certain NSEC wildcard\nproofs. A remote attacker could possibly use this issue to forge NXDOMAIN\nresponses and hide the existence of wildcard records. This issue only affected\nUbuntu 26.10. (CVE-2026-19941)\n\nIt was discovered that Bind incorrectly handled DNS-over-HTTPS requests\nwith invalid SIG(0) records. A remote attacker could possibly use this\nissue to cause Bind to crash, resulting in a denial of service. This issue only affected\nUbuntu 26.10. (CVE-2026-77692)\n\nIt was discovered that Bind incorrectly handled malformed zones\ncontaining NS or DNAME nodes above the zone origin. An attacker could\npossibly use this issue to cause Bind to serve out-of-zone records as\nauthoritative, leading to cache poisoning. This issue only affected\nUbuntu 26.10. (CVE-2026-78301)\n\nIt was discovered that Bind incorrectly handled SVCB/HTTPS AliasMode\nrecords referencing large numbers of ServiceMode records. A remote\nattacker could possibly use this issue to cause Bind to exhaust\nresources, leading to a denial of service. This issue only affected\nUbuntu 26.10. (CVE-2026-81563)\n\nIt was discovered that Bind incorrectly validated NSEC3 records from\nunrelated sibling zones. A remote attacker could possibly use this issue\nto perform a DNSSEC downgrade attack and have forged unsigned answers\naccepted. This issue only affected\nUbuntu 26.10. (CVE-2026-77119)\n\nIt was discovered that Bind incorrectly handled wildcard answers with\nmixed NSEC and NSEC3 proofs. A remote attacker could possibly use this\nissue to cause Bind to crash, resulting in a denial of service. This issue only affected\nUbuntu 26.10.\n(CVE-2026-80274)\n\nIt was discovered that Bind incorrectly handled oversized negative\ncache records. A remote attacker could possibly use this issue to cause\nBind to crash, resulting in a denial of service. This issue only affected\nUbuntu 26.10. (CVE-2026-19667)\n\nIt was discovered that Bind incorrectly handled cached trees of\nSVCB/HTTPS AliasMode records. A remote attacker could possibly use this\nissue to cause Bind to use excessive CPU resources, leading to a denial\nof service. This issue only affected\nUbuntu 26.10. (CVE-2026-81736)\n\nIt was discovered that Bind incorrectly limited the processing of\ncompression pointers in inbound DNS messages. A remote attacker could\npossibly use this issue to cause Bind to use excessive CPU and memory\nresources, leading to a denial of service. (CVE-2026-19630)\n\nIt was discovered that Bind incorrectly serialized access to shared\nGSS-TSIG security contexts. A remote attacker could possibly use this\nissue to corrupt memory and execute arbitrary code. (CVE-2026-94300)\n\nIt was discovered that Bind incorrectly handled redirect zones when\nused together with strict QNAME minimization. A remote attacker could\npossibly use this issue to cause Bind to crash, resulting in a denial\nof service. (CVE-2026-96888)\n\nIt was discovered that Bind incorrectly handled certain RPZ\nconfigurations when processing queries with and without recursion. A\nremote attacker could possibly use this issue to cause Bind to crash,\nresulting in a denial of service. (CVE-2026-97313)","status":"published","published":"2026-11-03T13:45:46Z","modified":"2026-11-03T21:34:46.680070301Z","updated_at":"2026-11-03T22:59:46.019912Z"}]}}