Skip to main content
Mallory
HighVulnerability

CVE-2026-81736: BIND 9 resolver CPU exhaustion through cached SVCB/HTTPS aliases

Published Sep 16, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 mentions · peak 3 in a dayToday
CVSS7.5High · v3.1
EPSS0.57%48th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-81736CWE-400

CVE-2026-81736 is a resource-exhaustion vulnerability in the BIND 9 recursive resolver. When the resolver has cached a tree of SVCB/HTTPS AliasMode records, a query for the root of that tree causes disproportionate CPU consumption during response construction. A remote attacker can exploit this behavior to disrupt DNS resolution. Affected versions are 9.18.0–9.18.50, 9.20.0–9.20.27, 9.21.0–9.21.25, 9.18.11-S1–9.18.50-S1, and 9.20.9-S1–9.20.27-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.

Exploitation can exhaust resolver CPU resources, degrading recursive DNS performance or causing denial of service for clients relying on the affected resolver. The vulnerability affects availability; no confidentiality or integrity impact is identified.

Mitigation

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

Restrict recursive resolution to trusted clients and networks where operationally feasible, and limit unnecessary network exposure of the resolver. Monitor CPU utilization, service availability, and anomalous SVCB/HTTPS query activity. Network segmentation and rate limiting may reduce attack exposure but do not correct the underlying excessive processing.

Remediation

Patch, then assume compromise.

Install a vendor security update that limits following HTTPS/SVCB aliases. Identified corrected releases include BIND 9.20.29, BIND Supported Preview Edition 9.20.29-S1, and BIND 9.21.26. Distribution-specific backports include Debian 12 bind9 1:9.18.49-1~deb12u3, Debian 13 bind9 1:9.20.29-1~deb13u1, RHEL 10.0 EUS bind 9.18.33-4.el10_0.6, and RHEL 9.6 bind9.18 9.18.29-4.el9_6.5. Use the security-fixed package applicable to the installed distribution and support stream rather than relying solely on the upstream version number.

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-81736 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-81736 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-81736?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-81736.
Is there a patch for CVE-2026-81736?
Install a vendor security update that limits following HTTPS/SVCB aliases. Identified corrected releases include BIND 9.20.29, BIND Supported Preview Edition 9.20.29-S1, and BIND 9.21.26.
What products are affected by CVE-2026-81736?
Internet Systems Consortium Bind.
How severe is CVE-2026-81736?
CVE-2026-81736 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.57% (48th percentile) as of Nov 6, 2026.
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 activity5Community discussion across Reddit, Mastodon, and other social sources.