Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCapture signed GSS-TSIG UDP message
-
DeliveryReplay within TSIG key validity window
-
ExploitSend crafted queries to attacker-controlled zone
-
ExecutionTrigger double-free memory corruption in named
-
ImpactAchieve potential remote code execution
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
|
| Exploitation Conditions | Exploitation requires that the targeted BIND 9 server use GSS-TSIG (Kerberos/GSS-API-negotiated transaction signatures) - this is a non-default, specialized configuration, typically paired with dynamic DNS update environments. The attacker must (1) be able to capture a previously GSS-TSIG-signed UDP message (requiring on-path or eavesdropping capability), (2) replay it while the negotiated TSIG key remains valid (a time-bounded window), and (3) control a DNS zone and send crafted queries to it. These requirements - passive capture capability, key-validity timing race, and an attacker-controlled zone - are the factors that limit real-world exploitation and justify the HIGH attack complexity, even though no authentication (PR:N) is needed. Affected versions span BIND 9.11.0-9.18.50, 9.20.0-9.20.29, 9.21.0-9.21.26, and the corresponding -S (subscription) builds; non-GSS-TSIG deployments are not exposed to this vector. |
| Impact | This is a genuine high-priority issue rather than an inflated high-CVSS number, though several signals temper its urgency. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N) describes an unauthenticated, network-reachable flaw with HIGH attack complexity, and the full C:H/I:H/A:H impact combined with CWE-415 (double free / use-after-free class memory corruption) in the core DNS daemon credibly supports the vendor's claim of potential remote code execution. The HIGH attack complexity is the dominant risk-limiting signal: exploitation is not a simple single-packet send - the attacker must first capture a previously GSS-TSIG-signed UDP message, replay it within the validity window of the negotiated TSIG key, and simultaneously drive crafted queries against a zone they control. No EPSS score was provided in the input, so exploitation probability cannot be quantified. KEV status is not present (no CISA listing supplied) and no POC was provided, so per the data this is 'no public exploit identified at time of analysis.' There is no SSVC decision data in the input. The net picture: a serious, patchable RCE candidate in ubiquitous software, but gated behind GSS-TSIG being configured and a non-trivial capture-and-replay precondition, which likely pushes real-world exploitation toward targeted rather than opportunistic/wormable activity. |
| Exploit ScenarioDerived | An attacker positioned to observe DNS traffic captures a GSS-TSIG-signed UDP message between a client and a BIND 9 resolver/server that uses GSS-TSIG. While the negotiated TSIG key is still valid, the attacker replays that signed message and simultaneously sends crafted queries to a DNS zone under their control, triggering a double-free memory-corruption condition in named that may be leveraged into remote code execution. No public exploit code was identified in the provided data, and the HIGH CVSS attack complexity reflects the capture, timing, and attacker-controlled-zone prerequisites. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in ISC BIND 9's GSS-TSIG handling allows an on-path attacker who captures a previously signed UDP message to replay it while the negotiated TSIG key remains valid; by combining the replay with crafted queries to an attacker-controlled zone, this can escalate to potential remote code execution on the named server. Affected releases are BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, and the subscription builds 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.29-S1. Exploitation requires the non-default GSS-TSIG (Kerberos-negotiated transaction signature) configuration plus passive capture capability, a timing race against key validity, and an attacker-controlled zone - constraints reflected in the HIGH attack complexity; no public exploit code was identified at time of analysis and there is no KEV listing.
RemediationAI
ISC has released fixed builds: upgrade to BIND 9.20.30 or 9.21.27 (downloads at https://downloads.isc.org/isc/bind9/9.20.30 and https://downloads.isc.org/isc/bind9/9.21.27), or the corresponding patched release on the branch you run per the advisory at https://kb.isc.org/docs/cve-2026-94300. Where immediate upgrade is not possible, the most effective compensating control is to disable GSS-TSIG for dynamic updates and fall back to static TSIG keys or restricted update ACLs - this removes the vulnerable code path entirely, at the cost of losing Kerberos-integrated automatic key negotiation and requiring manual key distribution. Because the attack requires capturing a signed UDP datagram, restricting the network path so GSS-TSIG update traffic cannot be passively observed (dedicated management VLANs, encrypted tunnels between update clients and the server, or source-IP ACLs limiting who may send signed updates) raises the bar substantially, though it does not fix the underlying double free and should be treated as temporary. Shortening TSIG key validity and rotating keys frequently narrows the replay window but adds operational overhead; monitoring for anomalous replayed update patterns or crashes of named provides detection while patches are staged.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BIND 9 is the widely deployed reference DNS server (named). GSS-TSIG extends classic TSIG by negotiating transaction signatures through GSS-API/Kerberos, so dynamic DNS updates can be authenticated against a Kerberos realm rather than static shared secrets; it is a specialized, non-default configuration typically found in Microsoft-AD-integrated dynamic DNS environments. The root cause class is CWE-415 (double free): replay of a previously GSS-TSIG-signed UDP message drives the signature-handling code into freeing an already-released memory structure, corrupting the heap. Because the flaw lives in signature/replay handling, the practical attack chain is capture-then-replay of a signed datagram within the negotiated key's validity window, followed by crafted queries directed at a zone the attacker controls to shape heap state toward code execution. The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H matches the assessment: remotely reachable without credentials, but with high complexity from the capture, timing, and configuration prerequisites. Deployments that do not use GSS-TSIG are not exposed to this vector.
Know when Bind 9 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable and unauthenticated (AV:N/PR:N), but AC:H because exploitation needs captured signed message, a TSIG-key timing window, and an attacker-controlled zone; memory corruption yields full C/I/A.
Primary rating from Vendor (isc).
CVSS VectorVendor: isc
DescriptionCVE.org
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "named". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
Executive ViewAI
ISC BIND 9, the DNS server software many organizations run for authoritative and recursive resolution, contains a high-severity memory corruption flaw in its GSS-TSIG handling that could allow an on-path attacker to replay signed messages and potentially achieve remote code execution on the named server. Organizations using the non-default GSS-TSIG Kerberos configuration are affected; a compromised DNS server can disrupt name resolution enterprise-wide, so leadership should prioritize confirmation of exposure and remediation timelines.
If immediate patching is not possible, disable GSS-TSIG where not strictly required, restrict UDP/53 exposure through network segmentation and ACLs, and monitor for replay or anomalous TSIG traffic; otherwise apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
BIND resolver servers performing DNSSEC validation can be forced into excessive CPU consumption when encountering a mali
Memory exhaustion in BIND 9 resolver allows unauthenticated remote attackers to cause denial of service by querying spec
Memory corruption in ISC BIND 9's DNS-over-HTTPS (DoH) implementation lets remote attackers trigger a use-after-free (CW
DNSSEC validation bypass in ISC BIND 9 resolvers (9.11.0 through 9.21.23 and S-editions) allows an attacker controlling
Denial of service in ISC BIND 9 lets a remote unauthenticated attacker exhaust resolver memory by flooding a DNSSEC-vali
Remote denial of service in ISC BIND 9 lets an attacker crash a validating resolver via a maliciously crafted DNSSEC pro
Denial of service in ISC BIND 9 resolvers (9.20.0-9.20.24, 9.21.0-9.21.23, and 9.20.9-S1-9.20.24-S1) lets remote unauthe
Cache poisoning in ISC BIND 9 recursive resolvers allows an attacker who controls an authoritative zone to inject forged
RPZ policy bypass and remote denial-of-service in ISC BIND 9 resolvers lets unauthenticated attackers defeat Response Po
Remote denial of service in ISC BIND 9 lets an off-path attacker crash a recursive resolver by controlling the timing an
Denial of service in ISC BIND 9 recursive resolvers affects versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.2
Remote denial of service in ISC BIND 9 lets an attacker-controlled (or spoofing-capable) authoritative DNS server crash
EUVD-2026-107254
GHSA-3g58-6x5w-h3fm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB