On this page (7 sections)
CVE-2026-88218 is a critical vulnerability in Windows DNS. According to its NVD record, a double free in Windows DNS allows an unauthorized attacker to execute code over a network. The record was published on 2026-11-10 and carries a CVSS score of 9.8.
If you run Windows DNS on a server that hosts websites, handles internal name resolution or backs an Active Directory environment, treat this as a priority item to track. The public information is still very short, so this article separates what is confirmed from what you will need to verify yourself.
What is confirmed so far
The only primary source available is the NVD entry, which repeats a one-sentence description. It also points to the Microsoft Security Response Center entry for this CVE as its reference. The research does not include the contents of that advisory.
That means the following are not confirmed here: the exact affected Windows versions, the fixed builds or update identifiers, whether a workaround exists, and whether anyone is exploiting the flaw. Only one independent publisher covers the story so far, so treat any claim beyond the description with caution until Microsoft's advisory confirms it.
What a double free means in plain terms
A double free (CWE-415) happens when a program releases the same block of memory twice. After the first release, the memory allocator may hand that block to something else. The second release then corrupts the allocator's bookkeeping, and an attacker who can shape what happens in between may turn the corruption into control over execution.
The CVE description says the attacker is unauthorized, meaning no valid credentials are needed, and that the attack happens over a network. A CVSS score of 9.8 is consistent with that kind of profile, but the research does not give the full vector, so details such as attack complexity or user interaction are not confirmed here.
DNS services are a sensitive target because they listen for requests by design and often run with high privileges on important servers. That is general context, not a statement about how this specific bug is triggered, which the sources do not describe.
Who is realistically exposed
- Servers with the Windows DNS Server role enabled, including domain controllers that also act as DNS servers.
- Any DNS server reachable from untrusted networks, especially if port 53 is open to the internet.
- Hosting and agency environments that run their own authoritative or recursive Windows DNS.
- Machines that only use DNS as a client are not described as affected in the available sources, but confirm this against Microsoft's advisory.
How to check your exposure
Start by finding out where the DNS Server role is installed. The following PowerShell command, run in an elevated session on a Windows Server, shows whether the role is installed. A result of Installed means the server needs attention.
Get-WindowsFeature -Name DNSNext, confirm that the DNS service is running. This command lists the service state; Running means it is active. Also note the Windows build so you can compare it with the fixed builds in Microsoft's advisory.
Get-Service -Name DNSThis command lists the installed updates with their install dates, so you can later confirm that the fix for this CVE was applied once Microsoft names it.
Get-HotFix | Sort-Object InstalledOn -DescendingWhat to do now
- Open the Microsoft advisory for CVE-2026-88218 and note the affected products and the update that fixes them.
- Inventory every server with the DNS Server role, including domain controllers and forgotten test machines.
- Install the Microsoft update for each affected system as soon as it is confirmed available, starting with internet-facing DNS servers and domain controllers.
- If you cannot patch immediately, restrict access to DNS ports with firewall rules so only expected clients and servers can reach them.
- Do not expose recursive DNS to the internet unless it is required.
- Check whether you still need the DNS Server role on each machine, and remove it where you do not.
- Record the patch date and build number per server so you can prove coverage later.
Detection and monitoring
Because no exploitation details are published in the sources, there are no confirmed indicators of compromise. Focus on general signals: unexpected crashes or restarts of the DNS service, unusual new processes spawned on DNS servers, and unexpected changes to DNS zones or records.
This command shows recent service control events for the DNS service, which can reveal unexpected stops or restarts. Run it in PowerShell on the DNS server and review any entries you cannot explain.
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Service Control Manager'} -MaxEvents 50 | Where-Object { $_.Message -like '*DNS*' }From the outside, you can also watch your public records for unplanned changes. Webforta Monitor tracks DNS and certificate changes, which can help you notice if records or certificates change unexpectedly. That is a monitoring aid, not a fix for this vulnerability. You can also spot-check a certificate with the free SSL checker.
What we do not know yet
- Which Windows Server versions and builds are affected.
- Which update fixes the flaw, and whether any mitigation exists.
- Whether the flaw is being exploited. The CVE data shows no CISA KEV listing, which is not proof that it is not exploited.
- The precise trigger or the full CVSS vector.
Treat these as open until Microsoft's advisory states them. If you read a claim about exploitation or affected versions elsewhere, check that it traces back to Microsoft rather than to another outlet repeating the same report.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
