The remote RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2026:54510 advisory.

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

    * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

    * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

    * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

    * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

    * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

Tenable has extracted the preceding description block directly from the RockyLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2026:54509 advisory.

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
      * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
      * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
      * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
      * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
      * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

Tenable has extracted the preceding description block directly from the AlmaLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:55437 advisory.

    The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols.
    BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing     with DNS); and tools for verifying that the DNS server is operating correctly.

    Security Fix(es):

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

    * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

    * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

    * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

    * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

    * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:55442 advisory.

    BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND     includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for     applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating     properly.

    Security Fix(es):

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)

    * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)

    * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)

    * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)

    * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)

    * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2026:55442 advisory.

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
      * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
      * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
      * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
      * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
      * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

Tenable has extracted the preceding description block directly from the AlmaLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote MiracleLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2026-1632:09 advisory.

    * bind9: bind: Potential wildcard CNAME RPZ policy bypass (CVE-2026-11331)
      * bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (CVE-2026-13321)
      * bind: bind9: Potential memory usage beyond configured limits (CVE-2026-11622)
      * bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards (CVE-2026-11721)
      * bind: bind9: Unexpected exit with NSEC and NSEC3 both present (CVE-2026-13204)
      * bind: bind9: Incorrect acceptance of NSEC3 records (CVE-2026-10723)

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2026:0929 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2026-10723:
    BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge     authenticated NXDOMAIN responses.
    This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

    CVE-2026-11622:
    A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can     suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver     can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured     in the max-cache-size parameter.
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

    CVE-2026-11721:
    It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of     labels than the zone in which the RRSIG is contained. This causes named to produce a wildcard name for a     zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to     have any effect, the resolver under attack must have set synth-from-dnssec yes; (which is the default).
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

    CVE-2026-13204:
    If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist     an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating     this proof.
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

    CVE-2026-13321:
    The BIND resolver accepts validly-signed NSEC records where the Next Domain Name field points outside     the signer's zone.
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1787734642 advisory.

  - BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge     authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0     through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
    (CVE-2026-10723)

  - An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query     names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled     correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9     software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0     through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1. (CVE-2026-11331)

  - A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can     suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver     can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured     in the `max-cache-size` parameter. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0     through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
    (CVE-2026-11622)

  - It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of     labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a     zone that is shorter than the attacker's zone, which can result in cache poisoning. For this attack to     have any effect, the resolver under attack must have set `synth-from-dnssec yes;` (which is the default).
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23,     9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1. (CVE-2026-11721)

  - If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist     an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating     this proof. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0     through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1. (CVE-2026-13204)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3484-1 advisory.

    This update for bind fixes the following issues

    - CVE-2026-11622: Potential memory usage beyond configured limits (bsc#1271986).
    - CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards     (bsc#1271987).
    - CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present (bsc#1271989).
    - CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field (bsc#1271990).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
335426	RockyLinux 9 : bind (RLSA-2026:54510)	Nessus	Rocky Linux Local Security Checks	2026/8/14	2026/8/14	high
335442	AlmaLinux 8 : bind9.16 (ALSA-2026:54509)	Nessus	Alma Linux Local Security Checks	2026/8/14	2026/8/14	high
335927	RHEL 10 : bind (RHSA-2026:55437)	Nessus	Red Hat Local Security Checks	2026/8/17	2026/8/17	high
335964	RHEL 9 : bind9.18 (RHSA-2026:55442)	Nessus	Red Hat Local Security Checks	2026/8/17	2026/8/17	high
338130	AlmaLinux 9 : bind9.18 (ALSA-2026:55442)	Nessus	Alma Linux Local Security Checks	2026/8/19	2026/8/19	high
339055	MiracleLinux 9 : bind-9.16.23-40.el9_8.8 (AXSA:2026-1632:09)	Nessus	Miracle Linux Local Security Checks	2026/8/24	2026/8/24	high
341126	TencentOS Server 3: bind (TSSA-2026:0929)	Nessus	Tencent Local Security Checks	2026/8/27	2026/8/27	high
351766	AlmaLinux 9.2 [TuxCare] Security Update: bind / bind-chroot / bind-devel / bind-dnssec-doc / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1787734642)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	high
332138	SUSE SLES12: bind / bind-chrootenv / bind-devel / bind-doc / bind-utils / etc (SUSE-SU-2026:3484-1)	Nessus	SuSE Local Security Checks	2026/8/5	2026/8/5	high

検出

プラグインの検索

high

high

high

high

high

high

high

high

high