Microsoft patches three RCE flaws in Windows DNS Server, including a heap overflow
Microsoft’s October and November 2026 Patch Tuesdays close three remote code execution flaws in the Windows DNS Server role, including CVE-2026-81384, a heap-based buffer overflow fixed on November 10. Any machine running the DNS role should be patched first — it is the phone book of an Active Directory domain.
October 13, 2026. Microsoft ships two remote code execution flaws in the DNS role of Windows Server. November 10, 2026. The November Patch Tuesday adds a third RCE, a heap-based buffer overflow tracked as CVE-2026-81384. November 10, 2026. All three flaws are reachable over the network without authentication. Why it matters: DNS is the directory of an Active Directory domain, and a compromised DNS server does not just fall over — it becomes the pivot for an intrusion into the whole domain.
November’s heap overflow
CVE-2026-81384 is the newest and most concerning of the batch. The NVD describes it as a heap-based buffer overflow (CWE-122) in the DNS server that lets an unauthorized attacker execute code over the network. Its CVSS 3.1 score is 8.1, on a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — that is no authentication, no user interaction, and low attack complexity.
The decisive part is the UI:N. On the other two DNS RCE flaws, Microsoft required user interaction — often a legitimate client triggering a resolution. Here, nothing of the sort: sending a single crafted DNS query or response is enough to corrupt the memory of the dns.exe process. The flaw was published on November 10, 2026, as part of the monthly Patch Tuesday, and it is not yet in the CISA KEV catalog — no in-the-wild exploitation has been confirmed, but a network-reachable heap overflow with no interaction is exactly the kind of primitive an actor turns into a quiet zero-day.
Two pointer dereferences left over from October
The other two RCE flaws were fixed a month earlier, on October 13, 2026, and share the same mechanism: an untrusted pointer dereference (CWE-822). Both CVE-2026-88114 and CVE-2026-88112 let an unauthorized attacker execute code over the network, at CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
The difference is the UI:R — user interaction is required, which Microsoft models here as the DNS server processing a specific request in a given context. That is one notch below November’s heap overflow, but the risk is still high: a DNS server is, by design, a machine clients query constantly. The interaction window is not an obstacle — it is the normal operating mode of the service.
The pattern is telling. Three RCE flaws across two patch cycles, all in the same component, all network-reachable with no privileges. This is not an isolated incident: it is a signal that Windows’ DNS server code — heir to a decades-old codebase — remains an active memory-corruption surface that Microsoft patches piecemeal.
The information disclosure that completes the picture
The same October batch closed a fourth flaw, less spectacular but consistent. CVE-2026-97826 is an out-of-bounds read (CWE-125) in the DNS server that lets an authorized attacker disclose information over the network. Its CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U) — a legitimate foothold is required, and the impact is confined to confidentiality.
Do not dismiss it. An out-of-bounds read in a name-resolution service can expose fragments of memory — records, session keys, sometimes adjacent secrets. Paired with an RCE, it becomes a reconnaissance primer: an attacker hunting a path into the server reads first, then writes. Together, the four flaws sketch a component that accumulates the classic memory-corruption classes — heap overflow, pointer dereference, out-of-bounds read — and that every Patch Tuesday closes only partially.
Why the DNS role is a prime target
The DNS server is not just another service. In an Active Directory domain it resolves the names of domain controllers, authentication services, and the whole internal zone. An attacker running code on a DNS server can poison resolution, redirect clients to machines they control, intercept legitimate queries, and pivot toward the domain controllers — the heart of the network.
That is a lesson we have already drawn from incidents covered on this blog. The Rebirthday campaign, which abused ECS to poison DNS caches, showed that a forged answer is enough to divert legitimate traffic. Quad9’s withdrawal from France was a reminder that DNS is also a sovereignty issue. Here the threat is more direct: it is not the resolution being forged, it is the server being owned.
The precedent is already on the record. In July 2020, CVE-2020-1350 — dubbed SIGRed — was a wormable RCE in the same Windows DNS server, patched out-of-band with a CVSS of 10. Four years later, the component still produces network-reachable, unauthenticated RCE flaws. The lesson is not to patch once: it is that Windows’ DNS server has not finished shipping this class of bug, so it must be patched in-cycle and hardened continuously.
A DNS server also sits directly in the path of authentication. When a workstation resolves the name of a domain controller, it is the DNS answer that decides which machine receives the Kerberos or NTLM request. Own the resolver and you can steer authentication traffic toward a host you control — which is why a DNS RCE is worth more than an RCE on a file server.
The operational consequence is simple. The DNS role often runs on the domain controllers themselves, or on dedicated servers that are, in effect, trust anchors of the domain. An RCE on those machines does not stop at the service — it opens OS-level access with the privileges of the dns.exe service account, typically a system account.
Remediation
The path forward comes down to two priorities. Apply the November 2026 Patch Tuesday — it carries the fix for CVE-2026-81384, the heap overflow. The October flaws (CVE-2026-88114, CVE-2026-88112, CVE-2026-97826) are already covered by October’s cumulative updates, but a machine that fell behind carries all four flaws at once.
# Check for the DNS role and the OS build
Get-WindowsFeature -Name DNS | Select-Object Name, InstallState
Get-ComputerInfo | Select-Object WindowsProductName, OsBuildNumber, OsVersion
# Install cumulative updates (adjust to your servicing channel)
Get-WindowsUpdate -Install -AcceptAll -AutoReboot Then shrink the surface. The DNS server should listen only on internal interfaces — never directly exposed to the internet. Segment it behind a firewall that allows only UDP/TCP 53 from legitimate clients, and watch for abnormal queries. If you cannot patch immediately, isolation is the temporary mitigation: pull the DNS server off any direct internet exposure and restrict which clients may query it — the flaws are network-reachable, so a narrowed reach directly lowers the odds of exploitation. Finally, isolate the role: if your estate allows, run DNS on dedicated machines rather than on domain controllers, to cap the blast radius of a compromise.
The verdict
If you run the Windows DNS Server role, apply the November 2026 Patch Tuesday now — CVE-2026-81384 is a heap overflow exploitable over the network with no authentication and no interaction. The priority goes to domain controllers and dedicated DNS servers, which are both the most exposed and the most valuable to an attacker.
If you have not caught up on October, the lag is doubly costly — you also carry the two pointer dereferences and the information disclosure. Beyond the patch, treat the DNS server as what it is: a trust anchor of the domain, not just another infrastructure service. Three RCE flaws in two months on the same component is the signal to patch fast and harden permanently.
References
- NVD — CVE-2026-81384 (Windows DNS Server Remote Code Execution Vulnerability)
- NVD — CVE-2026-88114 (Windows DNS Server Remote Code Execution Vulnerability)
- NVD — CVE-2026-88112 (Windows DNS Server Remote Code Execution Vulnerability)
- NVD — CVE-2026-97826 (Windows DNS Server Information Disclosure Vulnerability)
- MSRC — CVE-2026-88114 Security Update Guide