Skip to main content
Mallory
HighVulnerability

CVE-2026-76163: BIND 9 TKEY Query Assertion Failure Without Global Options

Published Sep 16, 2026 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 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-76163CWE-617 · Reachable Assertion

CVE-2026-76163 is a remotely exploitable denial-of-service vulnerability in ISC BIND 9. When the server configuration lacks a global options block, processing a DNS query with QTYPE TKEY may trigger an assertion failure and unexpectedly terminate the named process. Affected versions are 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and Supported Preview Edition 9.20.9-S1 through 9.20.27-S1. Exploitation requires no authentication or user interaction.

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 terminates the named process, disrupting DNS resolution or authoritative DNS service provided by that instance. Repeated exploitation can cause recurring service outages. No confidentiality or integrity impact is established for this vulnerability.

Mitigation

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

Ensure the active BIND configuration contains a global options block, removing the configuration condition required to trigger the vulnerability. Until updates are deployed, restrict DNS service access to trusted clients and networks where operationally feasible, and monitor for anomalous TKEY queries and unexpected named process exits.

Remediation

Patch, then assume compromise.

Apply the vendor security update for the installed BIND branch: BIND 9.20.29 or later, Supported Preview Edition 9.20.29-S1 or later, or development branch 9.21.26 or later. Distribution-maintained installations should use their applicable security-fixed packages; Debian 13 provides the fix in bind9 version 1:9.20.29-1~deb13u1 or later.

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-76163 exploited in the wild?
As of Nov 4, 2026, Mallory has no reports of CVE-2026-76163 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76163?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-76163.
Is there a patch for CVE-2026-76163?
Apply the vendor security update for the installed BIND branch: BIND 9.20.29 or later, Supported Preview Edition 9.20.29-S1 or later, or development branch 9.21.26 or later. Distribution-maintained installations should use their applicable security-fixed packages; Debian 13 provides the fix in bind9 version 1:9.20.29-1~deb13u1 or later.
What products are affected by CVE-2026-76163?
Internet Systems Consortium Bind.
How severe is CVE-2026-76163?
CVE-2026-76163 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.57% (48th percentile) as of Nov 4, 2026.
Activity feed

Recent activity

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

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