There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional
    processing, with no limit imposed by BIND. A DNS message with a maliciously large number of such
    structures will cause BIND to consume disproportionate amounts of CPU time and memory during processing.
    This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26,
    9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1. (CVE-2026-19630)

  - Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`". An attacker who can
    capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By
    also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote
    code execution. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0
    through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1. (CVE-2026-94300)

  - A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort
    with an assertion failure while processing the redirect. This issue affects BIND 9 versions 9.16.0 through
    9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1
    through 9.20.29-S1. (CVE-2026-96888)

  - A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive
    query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the
    BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default
    setting of "recursive-only yes", and the other with "recursive-only no". This issue affects BIND 9
    versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through
    9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1. (CVE-2026-97313)

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

  - A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort
    with an assertion failure while processing the redirect. This issue affects BIND 9 versions 9.16.0 through
    9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1
    through 9.20.29-S1. (CVE-2026-96888)

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

    Inbound-message resource exhaustion (CWE-400) leading to denial of service. No configuration precondition;
    version applicability is the deciding factor. Affected versions: 9.11.0-9.18.50, 9.20.0-9.20.29,     9.21.0-9.21.26. (CVE-2026-19630)

    A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of     a particular kind of invalid DNSSEC record.  Default limits on max-records-per-type and max-types-per-     name help mitigate the exposure.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-19668)

    A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading     a secure delegation and letting a forged unsigned answer through.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-77119)

    Replaying GSS-TSIG signed UDP messages can result in memory corruption in named. An attacker who can     capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By     also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote     code execution. (CVE-2026-94300)

    Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization (CWE-617). A     resolver is only affected when configured with both a redirect zone AND qname-minimization strict.
    Affected versions: 9.16.0-9.18.50, 9.20.0-9.20.29, 9.21.0-9.21.26. (CVE-2026-96888)

    Named exits on an assertion failure, resulting in denial of service. Affected versions: 9.16.0-9.18.50,     9.20.0-9.20.29. (CVE-2026-97313)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - A BIND resolver that is configured with both a redirect zone and qname-minimization strict may abort     with an assertion failure while processing the redirect. This issue affects BIND 9 versions 9.16.0 through     9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1     through 9.20.29-S1. (CVE-2026-96888)

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

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6576-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     October 21, 2026                      https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : bind9     CVE ID         : CVE-2026-19630 CVE-2026-94300 CVE-2026-96888 CVE-2026-97313

    Several vulnerabilities were discovered in BIND, a DNS server     implementation, which could result in denial of service or remote code     execution.

    For the stable distribution (trixie), these problems have been fixed in     version 1:9.20.30-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.

ID	Name	Product	Family	Published	Updated	Severity
476652	Alpine: multiple bind packages: security update to 9.20.30-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	10/22/2026	10/23/2026	high
476609	Echo: bind9: security update to 1:9.20.30-1~deb13u1	Tenable Cloud Security	Echo Local Security Checks	10/22/2026	10/22/2026	high
476652	Alpine: multiple bind packages: security update to 9.20.30-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	10/22/2026	10/23/2026	high
476609	Echo: bind9: security update to 1:9.20.30-1~deb13u1	Tenable Self-Hosted Container Security	Echo Local Security Checks	10/22/2026	10/22/2026	high
371851	Amazon Linux 2023 : bind, bind-chroot, bind-devel (ALAS2023-2026-3312)	Nessus	Amazon Linux Local Security Checks	10/25/2026	10/25/2026	high
370054	Linux Distros Unpatched Vulnerability : CVE-2026-96888	Nessus	Misc.	10/21/2026	10/26/2026	high
370219	Debian dsa-6576 : bind9 - security update	Nessus	Debian Local Security Checks	10/22/2026	10/26/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high