Skip to main content
Mallory
HighVulnerability

CVE-2026-11721: DNS cache poisoning in ISC BIND 9 through RRSIG label-count discrepancies

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

CVE-2026-11721 is a DNS cache-poisoning vulnerability in ISC BIND 9's handling of RRSIG label counts during DNSSEC-based wildcard synthesis. An attacker-controlled zone can return an RRSIG whose label count is smaller than the number of labels in the containing zone. The named process consequently constructs a wildcard name for a zone shorter than the attacker-controlled zone, potentially poisoning the resolver cache beyond that zone's boundaries. Exploitation requires synth-from-dnssec to be enabled, which is the default. Affected versions are 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

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 compromise DNS cache integrity by causing a resolver to synthesize and cache wildcard information extending beyond the attacker's zone. Clients relying on the affected resolver may subsequently receive incorrect DNS answers. Arbitrary code execution, privilege escalation, and direct confidentiality compromise are not established for this vulnerability.

Mitigation

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

Disable DNSSEC-based answer synthesis by setting synth-from-dnssec no; on affected resolvers and applying the configuration change. This removes the explicitly required exploitation condition and is a configuration-based mitigation inferred from that prerequisite. Restrict recursive service to trusted clients as defense in depth, but this alone does not prevent trusted clients from triggering resolution of attacker-controlled zones.

Remediation

Patch, then assume compromise.

Install a vendor-fixed BIND release or distribution security update explicitly addressing CVE-2026-11721. Distribution packages may contain backported fixes despite retaining upstream version numbers within the affected ranges. Fixed packages include Debian 13 bind9 version 1:9.20.26-1~deb13u1 and Ubuntu bind9 versions 1:9.20.24-1ubuntu0.4 for 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for 22.04 LTS. Use the applicable vendor security update for other releases and products bundling BIND.

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-11721 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-11721 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-11721?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-11721.
Is there a patch for CVE-2026-11721?
Install a vendor-fixed BIND release or distribution security update explicitly addressing CVE-2026-11721. Distribution packages may contain backported fixes despite retaining upstream version numbers within the affected ranges.
What products are affected by CVE-2026-11721?
Internet Systems Consortium Bind.
How severe is CVE-2026-11721?
CVE-2026-11721 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.40% (34th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
+59 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 activity7Community discussion across Reddit, Mastodon, and other social sources.