An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 45921d77-b346-11f1-952f-589cfc023192 advisory.

    ISC team reports:
    CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching     CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification     CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets     CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof     CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path     CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add()     CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver     CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work     amplification     CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request     CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees     CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement     CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts     CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof     CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references

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

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

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim
    resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the
    control of the attacker. If the auth responds with a particular sequence of crafted answers, and those
    answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-
    after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through
    9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19662)

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3137 advisory.

    For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a     zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that     does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server.
    Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit     the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945.This issue     affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1     through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19033)

    An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim     resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the     control of the attacker. If the auth responds with a particular sequence of crafted answers, and those     answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-     after-free bug, and abort.This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through     9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19662)

    On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is     malformed in a specific way, the resolver `named` process will exit unexpectedly.This issue affects BIND 9     versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through     9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19666)

    If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes,     then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read,     `named` aborts.This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0     through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19667)

    An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which     could allow an attacker at the same or an upstream level of the zone name to mask the existence of a     victim's wildcard record.This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through     9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
    (CVE-2026-19941)

    In a query response, an attacker may send `named` multiple copies of a record that should only exist once     (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-     memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other     memory attack vectors.This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27,     9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-75029)

    A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If     an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries     for names inside the configured zone then lose authoritative status and return an out-of-zone delegation.
    On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-     supplied data, affecting names outside the configured zone. This situation persists as long as the     malformed zone remains in the zone database.This issue affects BIND 9 versions 9.11.0 through 9.18.50,     9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through     9.20.27-S1. (CVE-2026-78301)

    If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server     replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same     owner name, it will trigger an unexpected program exit.This issue affects BIND 9 versions 9.11.0 through     9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1     through 9.20.27-S1. (CVE-2026-80274)

    A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode     records may fail to properly deallocate internal resources. If this happens repeatedly, resource     exhaustion will eventually prevent the resolver from performing new recursive lookups.This issue affects     BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through     9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-81563)

    If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of     that tree, the resolver will spend disproportionate CPU time constructing the response.This issue affects     BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through     9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-81736)

Tenable has extracted the preceding description block directly from the tested product 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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:4285-1 advisory.

    - CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification     (bsc#1280430).
    - CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).
    - CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).
    - CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).
    - CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).
    - CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof     (bsc#1280437).
    - CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work     amplification       (bsc#1280438).
    - CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement       (bsc#1280439).
    - CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).
    - CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request (bsc#1280441).
    - CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).
    - CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).
    - CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).
    - CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).

    Changes for bind:

    Upgrade to release 9.20.29

     New Features:
     * Disclose active Negative Trust Anchors with Extended DNS Error      33.
     Feature Changes:
     * Reject oversized and malformed DNSKEY records up front.
     * Speed up RPZ policy zone updates.
     Bug Fixes:
     * Prevent a crash when using both dns64 and filter-a.
     * Stop passing UDP client addresses to update-policy external      helpers.
     * Missing required NSEC3 for delegation not detected.
     * Tighten EUI48 and EUI64 text parsing.
     * GeoIP ACL state could be stale or wrong after reload.
     * Honor DNSSEC policy key tag ranges.
     * Fix a double free in mdig when EDNS options are specified.
     * Fix a crash when an IXFR falls back to AXFR with updates still      pending.
     * Fix DS requests to parental agents over TLS.
     * Fix the rndc-confgen -q (quiet) option.
     * Enforce query ACLs for redirect zones and searched DLZs.
     * Check asnum validity in GeoIP ACLs.
     * Fix a crash on remote-servers lists that reference themselves.
     * A record from outside a response policy zone could crash named.
     * Invalid key-store configuration could abort the DNSSEC tools.
     * NSEC signature set could bypass the secure-delegation check.
     * Fix a possible nsupdate issue when using GSS-TSIG.
     * Fix a crash with a single-element geoip sortlist.
     * Prevent out-of-bailiwick CNAMEs from evicting cached records.
     * Restore periodic cleanup of stale resolver address data.
     * Fix named-checkconf/named crash with malformed key name.
     * Prevent resolver crashes while processing DNS over TCP.
     * Ensure NSEC authority does not cross zonecut boundary.
     * Treat an unusable NSEC3 chain as a verification failure.
     * Treat non-canonical RPZ prefixes as any other failure.
     * Negative caching stopped working with      stale-answer-client-timeout set to 0.
     * An unterminated OpenSSL private-key Label: field could be read      past its parser buffer.
     * Restore SMF support on Solaris and illumos.
     * Fix compilation on GNU/Hurd.
     * dig +yaml was producing invalid YAML when a lookup failed.
     * Properly prevent TSIG generation command line injection      attacks.
     * Fix a potential heap bounds overflow write in dnssec-signzone.
     * Fix crashes on invalid DNSTAP input in dnstap-read.

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.

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6505 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6505-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     September 17, 2026                    https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : bind9     CVE ID         : CVE-2026-19033 CVE-2026-19662 CVE-2026-19666 CVE-2026-19667                      CVE-2026-19668 CVE-2026-75029 CVE-2026-76163 CVE-2026-77119                      CVE-2026-77692 CVE-2026-80274 CVE-2026-81563 CVE-2026-81736

    Several vulnerabilities were discovered in BIND, a DNS server implementation,     which may result in denial of service or cache poisoning.

    For the stable distribution (trixie), these problems have been fixed in     version 1:9.20.29-1~deb13u1.

    We recommend that you upgrade your bind9 packages.

    For the detailed security status of bind9 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/bind9

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim     resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the     control of the attacker. If the auth responds with a particular sequence of crafted answers, and those     answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-     after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through     9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. (CVE-2026-19662)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
362910	FreeBSD : bind920 -- multiple vulnerabilities (45921d77-b346-11f1-952f-589cfc023192)	Nessus	FreeBSD Local Security Checks	Local	medium
459864	Echo: bind9: security update to 1:9.20.29-1~deb13u1	Tenable Cloud Security	Echo Local Security Checks	Local	medium
459864	Echo: bind9: security update to 1:9.20.29-1~deb13u1	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
351047	Amazon Linux 2023 : bind, bind-chroot, bind-devel (ALAS2023-2026-3137)	Nessus	Amazon Linux Local Security Checks	Local	medium
349183	SUSE SLED15 / SLES15 Security Update : bind (SUSE-SU-2026:4285-1)	Nessus	SuSE Local Security Checks	Local	medium
346980	Debian dsa-6505 : bind9 - security update	Nessus	Debian Local Security Checks	Local	medium
346476	Linux Distros Unpatched Vulnerability : CVE-2026-19662	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-19662

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium