Skip to main content
Mallory
HighVulnerability

CVE-2026-11331: BIND 9 RPZ Wildcard CNAME Policy Bypass and Denial of Service

Published Jul 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days15 mentions · peak 3 in a dayToday
CVSS7.5High · v3.1
EPSS0.43%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-11331CWE-755

CVE-2026-11331 is an improper error-handling vulnerability in BIND 9 Response Policy Zone (RPZ) processing. When a resolver applies wildcard CNAME policies, specially crafted long query names can cause wildcard expansion to trigger a NAMETOOLONG error that is not handled correctly. This can bypass the applicable RPZ rule or cause BIND 9 to terminate unexpectedly. Affected versions are 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. Distribution packages may contain backported fixes despite retaining an upstream version within these ranges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can undermine DNS response-policy enforcement by defeating an applicable wildcard CNAME RPZ rule. It can also terminate the BIND process, interrupting DNS resolution for clients served by that process. Arbitrary code execution, privilege escalation, and direct sensitive-data disclosure are not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Avoid configuring RPZ wildcard CNAME policies until a fixed version is installed, accounting for the resulting loss or alteration of DNS policy enforcement. Restrict recursive DNS access to trusted clients to reduce exposure, although this does not prevent exploitation by an allowed client. On BIG-IP DNS, an alternative is to disable "Use BIND Server on BIG-IP" in the applicable DNS profile; this can affect configurations relying on BIND for fallback resolution.

Remediation

Patch, then assume compromise.

Install the vendor security update explicitly addressing CVE-2026-11331 for the deployed BIND package or appliance. Fixed distribution packages include Debian trixie bind9 1:9.20.26-1~deb13u1; Ubuntu 26.04 LTS 1:9.20.24-1ubuntu0.4, Ubuntu 24.04 LTS 1:9.18.39-0ubuntu0.24.04.8, and Ubuntu 22.04 LTS 1:9.18.39-0ubuntu0.22.04.7; and RHEL 9 bind 9.16.23-40.el9_8.8 for the applicable product stream. Use the corresponding advisory for other release streams rather than relying solely on upstream version comparisons. For BIG-IP DNS, install a release identified by F5 as containing the fix when available; no fixed BIG-IP DNS release was listed at advisory publication.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-11331 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-11331 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-11331?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-11331.
Is there a patch for CVE-2026-11331?
Install the vendor security update explicitly addressing CVE-2026-11331 for the deployed BIND package or appliance. Fixed distribution packages include Debian trixie bind9 1:9.20.26-1~deb13u1; Ubuntu 26.04 LTS 1:9.20.24-1ubuntu0.4, Ubuntu 24.04 LTS 1:9.18.39-0ubuntu0.24.04.8, and Ubuntu 22.04 LTS 1:9.18.39-0ubuntu0.22.04.7; and RHEL 9 bind 9.16.23-40.el9_8.8 for the applicable product stream.
What products are affected by CVE-2026-11331?
Internet Systems Consortium Bind.
How severe is CVE-2026-11331?
CVE-2026-11331 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.43% (38th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

74 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+53 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.