CVE-2026-62878 Overview
CVE-2026-62878 is a stack-based buffer overflow [CWE-121] in the Windows Domain Name System (DNS) service. An unauthenticated attacker can send crafted DNS traffic across the network and trigger memory corruption on the target host. Successful exploitation leads to arbitrary code execution in the context of the DNS service, which typically runs with elevated privileges on Windows Server systems.
The vulnerability requires no user interaction and no prior authentication. Microsoft published the advisory on 2026-08-11 and last updated the entry on 2026-08-12. The EPSS score is 0.907% at the 56.7 percentile as of 2026-08-13.
Critical Impact
Unauthenticated remote code execution against Windows DNS servers. Compromise of a DNS server can enable lateral movement, traffic redirection, and full domain compromise in Active Directory environments.
Affected Products
- Microsoft Windows (DNS Server role) — specific builds enumerated in the Microsoft advisory
- Windows Server versions running the DNS service (see Microsoft update guide for full list)
- Not Available — no CPE URIs were published in the NVD record at the time of writing
Discovery Timeline
- 2026-08-11 - CVE-2026-62878 published to NVD
- 2026-08-12 - Last updated in NVD database
Technical Details for CVE-2026-62878
Vulnerability Analysis
The flaw is categorized as a stack-based buffer overflow [CWE-121] in the Windows DNS service. A stack overflow occurs when a function writes more data into a fixed-size stack buffer than the buffer can hold. Adjacent stack data, including saved return addresses and frame pointers, gets overwritten.
In the context of a network-facing DNS server, the overflow is reached by parsing attacker-controlled DNS protocol data. An attacker who controls the length or content of a specific field can corrupt the stack and redirect execution. Because the DNS service handles queries and responses on UDP port 53 and TCP port 53, the attack surface is exposed to any host that can reach the server.
Exploitation yields code execution in the DNS service process. On Windows Server acting as a domain controller, that process runs with SYSTEM-level privileges, so a single successful exploit is sufficient to control the host.
Root Cause
The root cause is missing or incorrect bounds checking on a length or size field parsed from DNS network input. The affected code path copies attacker-controlled bytes into a stack buffer without verifying that the source length fits the destination. Microsoft has not published implementation-level details in the public advisory.
Attack Vector
The attack vector is network. An attacker sends a crafted DNS message to a vulnerable DNS server. No credentials and no user interaction are required. Servers that accept recursive queries from untrusted networks or forward queries to attacker-controlled zones present the largest exposure.
No verified public proof-of-concept code is available at the time of writing. Refer to the Microsoft CVE-2026-62878 Advisory for authoritative technical guidance.
Detection Methods for CVE-2026-62878
Indicators of Compromise
- Unexpected crashes or restarts of the dns.exe service, or Windows Error Reporting entries referencing the DNS service
- Anomalous DNS packets with malformed or oversized fields arriving on TCP/UDP port 53
- Child processes spawned by dns.exe (for example cmd.exe, powershell.exe, or rundll32.exe), which are not expected under normal operation
- Outbound network connections initiated by the DNS service to non-DNS destinations
Detection Strategies
- Alert on any process creation where the parent process is dns.exe, since legitimate DNS operation does not spawn interactive binaries
- Monitor for repeated DNS service crashes in the Windows Event Log (System log, source DNS-Server-Service)
- Inspect DNS traffic at the network edge for oversized records, malformed compression pointers, and abnormal query types
- Correlate DNS service anomalies with subsequent authentication or lateral movement events from the same host
Monitoring Recommendations
- Forward Windows Security, System, and DNS Server operational logs to a centralized SIEM for retention and correlation
- Enable command-line and process-creation auditing (Event ID 4688) on all Windows DNS servers
- Capture NetFlow or full packet capture on segments carrying DNS traffic to and from Internet-facing resolvers
How to Mitigate CVE-2026-62878
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft CVE-2026-62878 Advisory to all Windows DNS servers
- Prioritize domain controllers and Internet-facing DNS resolvers, since compromise of these hosts has the highest downstream impact
- Restrict inbound access to TCP/UDP port 53 so that only expected clients and upstream resolvers can reach the service
- Restart the DNS service or the host after patching to ensure the vulnerable code path is unloaded
Patch Information
Microsoft has released updates for the affected Windows versions. Consult the Microsoft CVE-2026-62878 Advisory for the specific KB article numbers, supported build ranges, and superseded updates. Deploy through Windows Update, WSUS, Microsoft Update Catalog, or your standard patch management pipeline.
Workarounds
- Block untrusted networks from reaching TCP/UDP port 53 on Windows DNS servers using host and perimeter firewalls
- Disable recursion on authoritative-only servers to reduce the parser surface exposed to arbitrary responses
- Where the DNS Server role is not required, remove it using Uninstall-WindowsFeature DNS on the affected host
# PowerShell: block external DNS access on a server not intended to serve public queries
New-NetFirewallRule -DisplayName "Restrict DNS Inbound" -Direction Inbound `
-Protocol UDP -LocalPort 53 -RemoteAddress 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 `
-Action Allow
New-NetFirewallRule -DisplayName "Block DNS Inbound External" -Direction Inbound `
-Protocol UDP -LocalPort 53 -Action Block
# Disable recursion on authoritative-only DNS servers
dnscmd /Config /NoRecursion 1
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

