{"schema":"vulnpedia.research/1","cve":"CVE-2026-97313","generated":"2026-10-26T13:52:32.101Z","references":[{"url":"https://kb.isc.org/docs/cve-2026-97313","tags":["vendor-advisory","vendor-reference"],"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","url":"https://kb.isc.org/docs/cve-2026-97313"},{"source":"nvd","sourceId":"CVE-2026-97313","modified":"2026-10-22T17:36:46.950","url":"https://kb.isc.org/docs/cve-2026-97313"},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://kb.isc.org/docs/cve-2026-97313"}]},{"url":"https://downloads.isc.org/isc/bind9/9.20.30","tags":["patch"],"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","url":"https://downloads.isc.org/isc/bind9/9.20.30"},{"source":"nvd","sourceId":"CVE-2026-97313","modified":"2026-10-22T17:36:46.950","url":"https://downloads.isc.org/isc/bind9/9.20.30"}]},{"url":"https://downloads.isc.org/isc/bind9/9.21.27","tags":["patch"],"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","origins":[{"source":"mitre","sourceId":"isc","modified":"2026-10-21T12:47:28.499Z","url":"https://downloads.isc.org/isc/bind9/9.21.27"},{"source":"nvd","sourceId":"CVE-2026-97313","modified":"2026-10-22T17:36:46.950","url":"https://downloads.isc.org/isc/bind9/9.21.27"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-97313","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://access.redhat.com/security/cve/CVE-2026-97313"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2556415","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2556415"}]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97313","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://www.cve.org/CVERecord?id=CVE-2026-97313"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97313","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97313"}]},{"url":"https://access.redhat.com/errata/RHSA-2026:87309","tags":["vendor-remediation"],"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://access.redhat.com/errata/RHSA-2026:87309"}]},{"source":"euvd","sourceId":"EUVD-2026-107256","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-107256","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-107256","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-107256"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-32:9.20.30-0.1.hum1@aarch64","product":"bind-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind@9.20.30-0.1.hum1?arch=aarch64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-32:9.20.30-0.1.hum1@s390x","product":"bind-32:9.20.30-0.1.hum1@s390x 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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind@9.20.30-0.1.hum1?arch=s390x&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-32:9.20.30-0.1.hum1@x86_64","product":"bind-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind@9.20.30-0.1.hum1?arch=x86_64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-chroot-32:9.20.30-0.1.hum1@aarch64","product":"bind-chroot-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-chroot@9.20.30-0.1.hum1?arch=aarch64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-chroot-32:9.20.30-0.1.hum1@x86_64","product":"bind-chroot-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-chroot@9.20.30-0.1.hum1?arch=x86_64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-devel-32:9.20.30-0.1.hum1@aarch64","product":"bind-devel-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-devel@9.20.30-0.1.hum1?arch=aarch64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-devel-32:9.20.30-0.1.hum1@s390x","product":"bind-devel-32:9.20.30-0.1.hum1@s390x 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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-devel@9.20.30-0.1.hum1?arch=s390x&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-dnssec-utils-32:9.20.30-0.1.hum1@aarch64","product":"bind-dnssec-utils-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-dnssec-utils@9.20.30-0.1.hum1?arch=aarch64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-dnssec-utils-32:9.20.30-0.1.hum1@s390x","product":"bind-dnssec-utils-32:9.20.30-0.1.hum1@s390x 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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-dnssec-utils@9.20.30-0.1.hum1?arch=s390x&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-doc-32:9.20.30-0.1.hum1@noarch@public-hummingbird-aarch64-rpms","product":"bind-doc-32:9.20.30-0.1.hum1@noarch@public-hummingbird-aarch64-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-doc@9.20.30-0.1.hum1?arch=noarch&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-doc-32:9.20.30-0.1.hum1@noarch@public-hummingbird-s390x-rpms","product":"bind-doc-32:9.20.30-0.1.hum1@noarch@public-hummingbird-s390x-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-doc@9.20.30-0.1.hum1?arch=noarch&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-doc-32:9.20.30-0.1.hum1@noarch@public-hummingbird-x86_64-rpms","product":"bind-doc-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-doc@9.20.30-0.1.hum1?arch=noarch&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-libs-32:9.20.30-0.1.hum1@s390x","product":"bind-libs-32:9.20.30-0.1.hum1@s390x 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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-libs@9.20.30-0.1.hum1?arch=s390x&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-libs-32:9.20.30-0.1.hum1@x86_64","product":"bind-libs-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-libs@9.20.30-0.1.hum1?arch=x86_64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-utils-32:9.20.30-0.1.hum1@s390x","product":"bind-utils-32:9.20.30-0.1.hum1@s390x 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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-utils@9.20.30-0.1.hum1?arch=s390x&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"Red Hat Hardened Images:bind-utils-32:9.20.30-0.1.hum1@x86_64","product":"bind-utils-32:9.20.30-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:87309"},{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."}],"purl":"pkg:rpm/redhat/bind-utils@9.20.30-0.1.hum1?arch=x86_64&epoch=32&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_6:bind-devel","product":"bind-devel as a component of Red Hat Enterprise Linux 6","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_7:bind-chroot","product":"bind-chroot as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-chroot","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-sdb","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_8:bind-chroot","product":"bind-chroot as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-chroot","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-license","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_8:bind-sdb","product":"bind-sdb as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-sdb","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_8:bind9.16-devel","product":"bind9.16-devel as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind9.16-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind9.16-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_9:bind-devel","product":"bind-devel as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_9:bind-utils","product":"bind-utils as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind-utils","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_9:bind9.18-doc","product":"bind9.18-doc as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/bind9.18-doc","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json","productId":"red_hat_enterprise_linux_9:dhcp-common","product":"dhcp-common as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:rpm/redhat/dhcp-common","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]},{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.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":"Ensure all Response Policy Zones (RPZ) configured in `/etc/named.conf` use identical `recursive-only` settings. For example, ensure all RPZ definitions consistently specify `recursive-only yes;` or `recursive-only no;`, eliminating conflicting policies.\n\nAlternatively, limit recursive query privileges strictly to authorized clients by configuring the `allow-recursion` option with an access control list (ACL).\n\nAfter modifying the configuration, validate the syntax and reload the service:\n\n```\nnamed-checkconf\nsystemctl reload named\n```\n\nCaveats:\nAligning the `recursive-only` setting across RPZ zones may alter policy enforcement behavior for non-recursive queries. Restricting recursion prevents unauthorized networks from performing recursive lookups.\n\nWarning:\nReloading or restarting the `named` service may cause a momentary pause in active DNS query processing."},{"category":"none_available","details":"Affected"}],"purl":"pkg:oci/ose-rhel-coreos-9?repository_url=registry.redhat.io/openshift/ose-rhel-coreos-9","origins":[{"source":"redhat","sourceId":"CVE-2026-97313","modified":"2026-10-22T05:32:46+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97313.json"}]}],"vendorCoverage":{"total":109,"shown":32,"omitted":77,"source":"redhat"}}