Skip to content
VulniPulse
Highest advisory severityHigh 2 vendors · 2 advisories

CVE-2026-11331

ISC BIND Vulnerability in NetApp Products

CVE-2026-11331: ISC BIND Vulnerability in NetApp Products. Not in the CISA KEV catalog. High advisory severity (CVSS 7.5, NetApp).

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

Get an email when NetApp publishes the next one.

VulniPulse checks NetApp's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

CVE-2026-11331 key facts

CISA KEV
Not listed (catalog checked )
Highest advisory severity
High
CVSS base score
7.5 (NetApp), 7.5 (Red Hat)
Fixed releases
  • Red Hat: bind-32:9.18.33-15.el10_2.10, bind9.16-32:9.16.23-0.22.el8_10.12, bind9.16-32:9.16.23-0.7.el8_6.11, bind9.16-32:9.16.23-0.14.el8_8.9, bind-32:9.16.23-40.el9_8.8, bind9.18-32:9.18.29-14.el9_8.8 and 22 more in the advisory
Vendor advisories
2 from NetApp, Red Hat
VulniPulse record
Published · Updated

Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-11331; bulletin-wide values are not repeated here.

Is CVE-2026-11331 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-11331 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-11331?

Upgrade to a fixed release named by the vendor:

  • Red Hat: bind-32:9.18.33-15.el10_2.10, bind9.16-32:9.16.23-0.22.el8_10.12, bind9.16-32:9.16.23-0.7.el8_6.11, bind9.16-32:9.16.23-0.14.el8_8.9, bind-32:9.16.23-40.el9_8.8, bind9.18-32:9.18.29-14.el9_8.8
  • To mitigate this issue, restrict resolver access to trusted networks and avoid using wildcard CNAME entries within Response Policy Zones (RPZ). 1. Edit `/etc/named.conf` to limit recursion and query caching to authorized client networks: ``` acl trusted_clients { 127.0.0.1; 192.168.1.0/24; }; options { allow-recursion { trusted_clients; }; allow-query-cache { trusted_clients; }; }; ``` Additionally, modify RPZ zone files to remove wildcard CNAME statements (such as `*.example.com CNAME target.com`), replacing them with explicit individual domain entries where feasible. 2. Reload the named service configuration: `systemctl reload named` Caveats: Restricting query access prevents untrusted external clients from resolving names through the server. Removing wildcard entries means unlisted subdomains will no longer be intercepted by the policy zone until explicit records are added. Warning: Reloading or restarting the named daemon may briefly disrupt ongoing DNS resolution. (Red Hat)

Vendor advisory comparison

NetApp

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-11331] ISC BIND Vulnerability in NetApp Products

    NTAP-20260730-0008Source published Source updated

    ISC BIND versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, and 9.21.0 through 9.21.23 are susceptible to a vulnerability which when successfully exploited could lead to disclosure of sensitive information. Successful exploitation of this vulnerability could lead to disclosure of sensitive information. NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 9.16.0
    • 9.18.50
    • 9.20.0
    • 9.20.24

    2 more entries in the full advisory.

    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-11331] Potential wildcard CNAME RPZ policy bypass

    CVE-2026-11331Source published Source updated

    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. A flaw was found in BIND. A remote attacker can send specially crafted, excessively long query names to a resolver configured with Response Policy Zones (RPZ) and wildcard policies. Improper handling of the resulting error condition can cause the service to terminate unexpectedly, leading to a Denial of…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
    • Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On
    • Red Hat Enterprise Linux 8.8 Telecommunications Update Service

    10 more entries in the full advisory.

    Source-reported affected versions
    • 9.16.0
    • 9.18.50
    • 9.20.0
    • 9.20.24

    4 more entries in the full advisory.

    Source-reported fixed versions
    • bind-32:9.18.33-15.el10_2.10
    • bind9.16-32:9.16.23-0.22.el8_10.12
    • bind9.16-32:9.16.23-0.7.el8_6.11
    • bind9.16-32:9.16.23-0.14.el8_8.9

    24 more entries in the full advisory.

    Mitigation guidance
    • To mitigate this issue, restrict resolver access to trusted networks and avoid using wildcard CNAME entries within Response Policy Zones (RPZ). 1. Edit `/etc/named.conf` to limit recursion and query caching to authorized client networks: ``` acl trusted_clients { 127.0.0.1; 192.168.1.0/24; }; options { allow-recursion { trusted_clients; }; allow-query-cache { trusted_clients; }; }; ``` Additionally, modify RPZ zone files to remove wildcard CNAME statements (such as `*.example.com CNAME target.com`), replacing them with explicit individual domain entries where feasible. 2. Reload the named service configuration: `systemctl reload named` Caveats: Restricting query access prevents untrusted external clients from resolving names through the server. Removing wildcard entries means unlisted subdomains will no longer be intercepted by the policy zone until explicit records are added. Warning: Reloading or restarting the named daemon may briefly disrupt ongoing DNS resolution.
All NetApp advisories

Follow CVE-2026-11331 in the free weekly digest

Every Monday: whether it was added to CISA KEV, reported exploited, got a fix or changed severity, plus the week's critical and high advisories.

Free, no account. Confirm by email; unsubscribe in one click. Choose vendors and severity

Browse the latest tracked CVEs or the CVEs listed in CISA KEV.

Android app · Google Play

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery