Security alert · Critical
Windows DNS CVE-2026-88218: critical remote code execution flaw, CVSS 9.8
· 2 minutes read · Centoculus Security Team
Known since
Affected: Windows DNS. For affected Windows versions and updates, see the Microsoft advisory
What happened
Microsoft disclosed CVE-2026-88218 on 10 November 2026. Microsoft describes it as a double free in Windows DNS that "allows an unauthorized attacker to execute code over a network". An attacker needs no account and no login. The vulnerability has a CVSS base score of 9.8 (critical).
We know of no attacks so far. CISA has not listed the vulnerability in its catalogue of known exploited vulnerabilities. Microsoft has not published technical details about the flaw.
Who is affected
According to the description, the vulnerability is in Windows DNS. The catalogue entry we used names Microsoft Exchange as the product, but the vulnerability description itself only mentions Windows DNS. Microsoft's advisory, linked below, is the reference for which Windows and Windows Server versions are affected. Our data does not list affected or fixed versions.
Check these systems first:
- Windows Servers running the DNS Server role, including Active Directory domain controllers, which usually provide DNS
- Windows DNS servers that can be reached from the internet or from untrusted networks
Linux servers and their DNS software (for example BIND, Unbound or PowerDNS) are not affected. This vulnerability concerns Windows only.
What to do now
- Open Microsoft's advisory for CVE-2026-88218, linked below. Note which Windows versions are listed and which security updates fix them.
- Install those security updates through Windows Update, WSUS or your patch management tool. Start with DNS servers and domain controllers, then do the remaining Windows servers.
- Restart the servers if the update asks for it. Then check that the DNS Server service is running (
Get-Service DNSin PowerShell) and that name resolution works (for exampleResolve-DnsName example.com -Server localhost). - Until every server is updated, make sure Windows DNS servers cannot be reached from the internet. Allow DNS traffic on port 53 (UDP and TCP) only from networks that need it.
- Check the event logs of your DNS servers for unexpected crashes or restarts of the DNS Server service (System log and the DNS Server log). Microsoft has not published specific signs of an attack.
How to check whether you are affected
- Find servers with the DNS Server role: run
Get-WindowsFeature DNSin PowerShell, or check Server Manager. - Use
Get-HotFixor the update history to see whether the update Microsoft lists for your Windows version is installed. If it is not, the server is vulnerable. - Check your firewall rules to see whether port 53 on your Windows servers can be reached from the internet.
Sources
More on Microsoft Exchange
- Windows Media Foundation: critical remote code execution flaw (CVE-2026-96157)
- Microsoft Color Management: critical remote code execution flaw (CVE-2026-96078)
- Microsoft Exchange: critical remote code execution via Color Management (CVE-2026-96067)
- Windows DHCP Server: critical remote code execution flaw (CVE-2026-88243)
- Windows iSCSI: critical remote code execution flaw CVE-2026-88234 (CVSS 9.8)
- Windows Kerberos CVE-2026-85844: authentication bypass allows privilege escalation
- Microsoft SharePoint: critical privilege escalation flaw (CVE-2026-120002)
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.