NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
HIGH severity

CVE-2026-11331 — bind9

HIGH

CVE-2026-11331 is a high-severity (CVSS 7.5) CWE-790 vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-11331.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.4%0.4%0.4%0.4%0.4%Aug 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Description

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.

Affected Products

1 product · 5 configurations
Application
bindisc
≥ 9.21.0 && ≤ 9.21.23
range

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    The records we use list no fixed release for CVE-2026-11331. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as Important because an unauthenticated remote client can terminate the DNS resolver service or bypass security filtering policies. In default Red Hat Enterprise Linux installations, Response Policy Zones (RPZ) are not configured and require explicit administrative definition. The flaw…

Workaround published by Red Hat
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…
Source: Red Hat security advisory for CVE-2026-11331 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10bind-32:9.18.33-15.el10_2.10RHSA-2026:55437
Red Hat Enterprise Linux 10.0 Extended Update Supportbind-32:9.18.33-4.el10_0.6RHSA-2026:94115
Red Hat Enterprise Linux 8bind9.16-32:9.16.23-0.22.el8_10.12RHSA-2026:54509
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportbind9.16-32:9.16.23-0.7.el8_6.11RHSA-2026:80501
Red Hat Enterprise Linux 8.8 Telecommunications Update Servicebind9.16-32:9.16.23-0.14.el8_8.9RHSA-2026:79160
Red Hat Enterprise Linux 9bind-32:9.16.23-40.el9_8.8RHSA-2026:54510
Red Hat Enterprise Linux 9bind9.18-32:9.18.29-14.el9_8.8RHSA-2026:55442
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionsbind-32:9.16.23-11.el9_2.12RHSA-2026:95242

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-11331 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

CVE-2026-11331: bind9 (High 7.5)