{"schema":"vulnpedia.research/1","cve":"CVE-2026-19668","generated":"2026-10-26T13:52:32.101Z","references":[{"url":"https://kb.isc.org/docs/cve-2026-19668","tags":["vendor-advisory","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","url":"https://kb.isc.org/docs/cve-2026-19668"},{"source":"nvd","sourceId":"CVE-2026-19668","modified":"2026-09-17T19:16:42.057","url":"https://kb.isc.org/docs/cve-2026-19668"},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://kb.isc.org/docs/cve-2026-19668"}]},{"url":"https://downloads.isc.org/isc/bind9/9.20.29","tags":["patch","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","url":"https://downloads.isc.org/isc/bind9/9.20.29"},{"source":"nvd","sourceId":"CVE-2026-19668","modified":"2026-09-17T19:16:42.057","url":"https://downloads.isc.org/isc/bind9/9.20.29"},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://downloads.isc.org/isc/bind9/9.20.29"}]},{"url":"https://downloads.isc.org/isc/bind9/9.21.26","tags":["patch","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-09-16T14:12:34.380Z","url":"https://downloads.isc.org/isc/bind9/9.21.26"},{"source":"nvd","sourceId":"CVE-2026-19668","modified":"2026-09-17T19:16:42.057","url":"https://downloads.isc.org/isc/bind9/9.21.26"},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://downloads.isc.org/isc/bind9/9.21.26"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-19668","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://access.redhat.com/security/cve/CVE-2026-19668"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535476","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2535476"}]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-19668","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://www.cve.org/CVERecord?id=CVE-2026-19668"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19668","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19668"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:68279","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://access.redhat.com/errata/RHSA-2026:68279"}]},{"source":"euvd","sourceId":"EUVD-2026-80783","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-80783","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-80783","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-80783"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-0:9.20.29-0.1.hum1@aarch64","product":"bind-0:9.20.29-0.1.hum1@aarch64 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind@9.20.29-0.1.hum1?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-0:9.20.29-0.1.hum1@src","product":"bind-0:9.20.29-0.1.hum1@src 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind@9.20.29-0.1.hum1?arch=src&distro=hummingbird-20251124&repository_id=public-hummingbird-source-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-chroot-0:9.20.29-0.1.hum1@aarch64","product":"bind-chroot-0:9.20.29-0.1.hum1@aarch64 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-chroot@9.20.29-0.1.hum1?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-chroot-0:9.20.29-0.1.hum1@x86_64","product":"bind-chroot-0: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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-chroot@9.20.29-0.1.hum1?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-devel-0:9.20.29-0.1.hum1@x86_64","product":"bind-devel-0: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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-devel@9.20.29-0.1.hum1?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-dnssec-utils-0:9.20.29-0.1.hum1@aarch64","product":"bind-dnssec-utils-0:9.20.29-0.1.hum1@aarch64 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-dnssec-utils@9.20.29-0.1.hum1?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-dnssec-utils-0:9.20.29-0.1.hum1@x86_64","product":"bind-dnssec-utils-0: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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-dnssec-utils@9.20.29-0.1.hum1?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-doc-0:9.20.29-0.1.hum1@noarch@public-hummingbird-x86_64-rpms","product":"bind-doc-0:9.20.29-0.1.hum1@noarch@public-hummingbird-x86_64-rpms 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-doc@9.20.29-0.1.hum1?arch=noarch&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-libs-0:9.20.29-0.1.hum1@aarch64","product":"bind-libs-0:9.20.29-0.1.hum1@aarch64 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-libs@9.20.29-0.1.hum1?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-utils-0:9.20.29-0.1.hum1@aarch64","product":"bind-utils-0:9.20.29-0.1.hum1@aarch64 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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-utils@9.20.29-0.1.hum1?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"Red Hat Hardened Images:bind-utils-0:9.20.29-0.1.hum1@x86_64","product":"bind-utils-0: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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."}],"purl":"pkg:rpm/redhat/bind-utils@9.20.29-0.1.hum1?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_10:bind-utils","product":"bind-utils as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_7:bind-libs-lite","product":"bind-libs-lite as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-libs-lite","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-sdb","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_8:bind-export-libs","product":"bind-export-libs as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-export-libs","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_8:bind-pkcs11-libs","product":"bind-pkcs11-libs as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-pkcs11-libs","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind9.16-chroot","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_8:python3-bind","product":"python3-bind as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/python3-bind","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_9:bind-doc","product":"bind-doc as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind-doc","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json","productId":"red_hat_enterprise_linux_9:bind9.18-dnssec-utils","product":"bind9.18-dnssec-utils as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"To mitigate potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/bind9.18-dnssec-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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 potential denial of service, ensure that the BIND recursive resolver's configuration includes appropriate limits for `max-records-per-type` and `max-types-per-name` within the `named.conf` file. These settings help control resource consumption when encountering invalid DNSSEC records. A restart of the `named` service is required for any configuration changes to take effect."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:oci/ose-rhel-coreos-9@4.22.9.8.202609081748-0?repository_url=registry.redhat.io/openshift/ose-rhel-coreos-9","origins":[{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]},{"source":"redhat","sourceId":"CVE-2026-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.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-19668","modified":"2026-09-21T11:37:41+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-19668.json"}]}],"vendorCoverage":{"total":102,"shown":32,"omitted":70,"source":"redhat"}}