Skip to main content
Mallory
HighVulnerability

CVE-2026-81563: BIND 9 SVCB/HTTPS AliasMode Resource Exhaustion

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-81563CWE-772

CVE-2026-81563 is a resource-release vulnerability in the BIND 9 recursive resolver's SVCB/HTTPS AliasMode processing. Following an AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may leave internal resources allocated, leaking resolver cache memory. Repeated processing can exhaust resources and prevent new recursive lookups. 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.

Repeated triggering causes cumulative resolver memory or resource exhaustion, eventually denying new recursive DNS lookups and disrupting services that depend on the resolver. No confidentiality or integrity impact is established for this vulnerability.

Mitigation

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

Pending patching, restrict recursive-query access to trusted clients and networks where feasible, reduce unnecessary DNS service exposure, and use network segmentation and rate limiting to reduce opportunities for repeated triggering. Monitor resolver resource consumption and DNS availability. These measures reduce exposure but do not correct the resource leak; no vulnerability-specific workaround is established.

Remediation

Patch, then assume compromise.

Install the applicable vendor security-fixed BIND packages. Supported upgrade targets identified in security guidance include BIND 9.20.29 or later, BIND 9.21.26 or later, and Supported Preview Edition 9.20.29-S1 or later. Distribution backports also address the vulnerability, including Debian 12 bind9 1:9.18.49-1~deb12u3, 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 fixed package appropriate to the installed distribution and support stream rather than assessing backported packages solely by their upstream version.

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-81563 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-81563 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-81563?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-81563.
Is there a patch for CVE-2026-81563?
Install the applicable vendor security-fixed BIND packages. Supported upgrade targets identified in security guidance include BIND 9.20.29 or later, BIND 9.21.26 or later, and Supported Preview Edition 9.20.29-S1 or later.
What products are affected by CVE-2026-81563?
Internet Systems Consortium Bind.
How severe is CVE-2026-81563?
CVE-2026-81563 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.