{"schema":"vulnpedia.research/1","cve":"CVE-2026-19662","generated":"2026-10-26T13:52:32.101Z","references":[{"url":"https://kb.isc.org/docs/cve-2026-19662","tags":["vendor-advisory","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-09-16T13:50:10.432Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-09-16T13:50:10.432Z","url":"https://kb.isc.org/docs/cve-2026-19662"},{"source":"nvd","sourceId":"CVE-2026-19662","modified":"2026-09-17T19:16:41.783","url":"https://kb.isc.org/docs/cve-2026-19662"},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://kb.isc.org/docs/cve-2026-19662"}]},{"url":"https://downloads.isc.org/isc/bind9/9.20.29","tags":["patch","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-09-16T13:50:10.432Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-09-16T13:50:10.432Z","url":"https://downloads.isc.org/isc/bind9/9.20.29"},{"source":"nvd","sourceId":"CVE-2026-19662","modified":"2026-09-17T19:16:41.783","url":"https://downloads.isc.org/isc/bind9/9.20.29"},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://downloads.isc.org/isc/bind9/9.20.29"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19662","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://access.redhat.com/security/cve/CVE-2026-19662"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535445","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535445"}]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19662","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://www.cve.org/CVERecord?id=CVE-2026-19662"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19662","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19662"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:89745","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://access.redhat.com/errata/RHSA-2026:89745"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:89746","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://access.redhat.com/errata/RHSA-2026:89746"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:68279","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://access.redhat.com/errata/RHSA-2026:68279"}]},{"source":"euvd","sourceId":"EUVD-2026-80743","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-80743","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-80743","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-80743"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind-32:9.16.23-40.el9_8.12.aarch64","product":"bind-32:9.16.23-40.el9_8.12.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89745"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind@9.16.23-40.el9_8.12?arch=aarch64&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind-debugsource-32:9.16.23-40.el9_8.12.x86_64","product":"bind-debugsource-32:9.16.23-40.el9_8.12.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89745"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind-debugsource@9.16.23-40.el9_8.12?arch=x86_64&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind-libs-debuginfo-32:9.16.23-40.el9_8.12.x86_64","product":"bind-libs-debuginfo-32:9.16.23-40.el9_8.12.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89745"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind-libs-debuginfo@9.16.23-40.el9_8.12?arch=x86_64&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind9.18-chroot-32:9.18.29-14.el9_8.11.ppc64le","product":"bind9.18-chroot-32:9.18.29-14.el9_8.11.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89746"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind9.18-chroot@9.18.29-14.el9_8.11?arch=ppc64le&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind9.18-dnssec-utils-debuginfo-32:9.18.29-14.el9_8.11.ppc64le","product":"bind9.18-dnssec-utils-debuginfo-32:9.18.29-14.el9_8.11.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89746"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind9.18-dnssec-utils-debuginfo@9.18.29-14.el9_8.11?arch=ppc64le&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"AppStream-9.8.0.Z.MAIN.EUS:bind9.18-utils-debuginfo-32:9.18.29-14.el9_8.11.s390x","product":"bind9.18-utils-debuginfo-32:9.18.29-14.el9_8.11.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89746"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind9.18-utils-debuginfo@9.18.29-14.el9_8.11?arch=s390x&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"CRB-9.8.0.Z.MAIN.EUS:bind-devel-32:9.16.23-40.el9_8.12.s390x","product":"bind-devel-32:9.16.23-40.el9_8.12.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89745"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind-devel@9.16.23-40.el9_8.12?arch=s390x&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"CRB-9.8.0.Z.MAIN.EUS:bind-utils-debuginfo-32:9.16.23-40.el9_8.12.ppc64le","product":"bind-utils-debuginfo-32:9.16.23-40.el9_8.12.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89745"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind-utils-debuginfo@9.16.23-40.el9_8.12?arch=ppc64le&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"CRB-9.8.0.Z.MAIN.EUS:bind9.18-devel-32:9.18.29-14.el9_8.11.s390x","product":"bind9.18-devel-32:9.18.29-14.el9_8.11.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89746"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind9.18-devel@9.18.29-14.el9_8.11?arch=s390x&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"CRB-9.8.0.Z.MAIN.EUS:bind9.18-utils-debuginfo-32:9.18.29-14.el9_8.11.s390x","product":"bind9.18-utils-debuginfo-32:9.18.29-14.el9_8.11.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 9)","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258","url":"https://access.redhat.com/errata/RHSA-2026:89746"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind9.18-utils-debuginfo@9.18.29-14.el9_8.11?arch=s390x&epoch=32","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"Red Hat Hardened Images:bind-utils-32:9.20.29-0.1.hum1@x86_64","product":"bind-utils-32:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images","status":"fixed","remediations":[{"category":"vendor_fix","details":"For details on how to apply this update, which includes the changes described in this advisory, refer to:\nhttps://images.redhat.com/","url":"https://access.redhat.com/errata/RHSA-2026:68279"},{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"}],"purl":"pkg:rpm/redhat/bind-utils@9.20.29-0.1.hum1?arch=x86_64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_10:bind","product":"bind as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_10:bind-license","product":"bind-license as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_7:bind-devel","product":"bind-devel as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_7:bind-license","product":"bind-license as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_7:bind-sdb","product":"bind-sdb as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-sdb","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_8:bind-devel","product":"bind-devel as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_8:bind-license","product":"bind-license as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_8:bind-pkcs11-utils","product":"bind-pkcs11-utils as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-pkcs11-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_8:bind9.16-chroot","product":"bind9.16-chroot as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind9.16-chroot","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_8:bind9.16-utils","product":"bind9.16-utils as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind9.16-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_openshift_container_platform_4:openshift/ose-rhel-coreos-9","product":"openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate this issue, consider disabling DNSSEC validation on `named` resolvers if it is not a strict requirement for your environment. This can be achieved by setting `dnssec-validation no;` in the `named.conf` file. Disabling DNSSEC validation will prevent the resolver from processing DNSSEC-signed zones, thereby avoiding this specific vulnerability, but it will also remove the security benefits provided by DNSSEC. After modifying the configuration, the `named` service must be reloaded or restarted for the changes to take effect.\n\n`sudo systemctl reload named`\n`sudo systemctl restart named`"},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:oci/ose-rhel-coreos-9?repository_url=registry.redhat.io/openshift/ose-rhel-coreos-9","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind","product":"bind as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind-chroot","product":"bind-chroot as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind-chroot","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind-devel","product":"bind-devel as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind-sdb","product":"bind-sdb as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind-sdb","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind-utils","product":"bind-utils as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_6:bind.src","product":"bind.src as a component of Red Hat Enterprise Linux 6","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/bind?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_9:dhcp-client","product":"dhcp-client as a component of Red Hat Enterprise Linux 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/dhcp-client","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_9:dhcp-relay","product":"dhcp-relay as a component of Red Hat Enterprise Linux 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/dhcp-relay","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_9:dhcp-server","product":"dhcp-server as a component of Red Hat Enterprise Linux 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/dhcp-server","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]},{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json","productId":"red_hat_enterprise_linux_9:dhcp.src","product":"dhcp.src as a component of Red Hat Enterprise Linux 9","status":"known_not_affected","remediations":[],"justification":"vulnerable_code_not_present","purl":"pkg:rpm/redhat/dhcp?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-19662","modified":"2026-10-26T07:13:59+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19662.json"}]}],"vendorCoverage":{"total":232,"shown":32,"omitted":200,"source":"redhat"}}