Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Windows DNS Server over network
  2. Delivery
    Induce resolution of attacker-controlled DNS records
  3. Exploit
    Trigger untrusted pointer dereference in parser
  4. Execution
    Execute arbitrary code in DNS service
  5. Impact
    Pivot to domain/host compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Untrusted pointer prevention
Exploitation Conditions

The target must have the Windows DNS Server role installed and reachable by the attacker. Exploitation is inferred to require the server to process an attacker-influenced DNS response - most plausibly a recursive/forwarding resolver that can be induced to query attacker-controlled records that trigger the untrusted pointer dereference during parsing. The UI:R metric is the key limiting factor: a triggering action or interaction is needed rather than a purely unsolicited inbound packet, which narrows opportunistic internet-wide exploitation. No authentication is required (PR:N). Affected builds span Windows Server 2016/2019/2022/2025 and Windows 10/11 client builds below the patched versions listed in EUVD; systems without the DNS Server role or already patched are not exposed.

Impact

This is a genuine high-priority vulnerability, though not quite emergency-tier. The CVSS 3.1 base score of 8.8 reflects network-reachable (AV:N), low-complexity (AC:L) code execution by an unauthorized attacker (PR:N) with full confidentiality/integrity/availability impact (C:H/I:H/A:H), tempered only by a user-interaction requirement (UI:R). The affected component - Windows DNS Server - is a high-value target because it is frequently co-located on Active Directory domain controllers, so code execution there can cascade into full domain compromise. Countervailing signals keep this below a drop-everything rating: no EPSS score was provided in the input, there is no CISA KEV listing, and no public exploit code was identified, so exploitation status is 'no public exploit identified at time of analysis.' The vulnerability was reported privately by Microsoft's own security team (secure@microsoft.com), which is consistent with internal/coordinated discovery rather than observed in-the-wild attacks. One data conflict must be flagged: the input Tag 'Authentication Bypass' contradicts the CWE-822 (untrusted pointer dereference) classification and the description's 'execute code' impact - treat the tag as unreliable and the memory-corruption RCE framing as authoritative. Net: patch promptly, especially on internet-adjacent or recursive resolvers, but current data does not indicate active mass exploitation.

Exploit ScenarioDerived

An attacker induces a vulnerable Windows DNS Server to process a maliciously crafted DNS response - for example by getting the server (acting as a recursive resolver) to query an attacker-controlled domain whose records trigger an untrusted pointer dereference during parsing. The UI:R metric indicates some triggering action or interaction is required rather than a fully passive packet drop, after which the attacker achieves arbitrary code execution in the DNS service context. No public exploit code was identified at the time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Untrusted pointer dereference in Microsoft Windows DNS Server enables a remote, unauthenticated attacker to execute arbitrary code in the context of the DNS service on an affected host. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms no authentication is required but also shows that some triggering interaction or processing of an attacker-influenced DNS response is needed, which meaningfully narrows opportunistic internet-wide exploitation compared with a purely unsolicited inbound-packet bug. Exposure is limited to Windows Server 2016/2019/2022/2025 (including Server Core) and supported Windows 10/11 client builds running the DNS Server role below the patched build levels; no public exploit code and no confirmed active exploitation were identified at time of analysis, but the high severity and network reachability justify prompt patching.

RemediationAI

Vendor-released patch: Microsoft has published fixes via its update guide, and each affected build must be raised to or above the corresponding patched level - 10.0.14393.9612 for Windows Server 2016/Windows 10 1607, 10.0.17763.9376 for Server 2019/Windows 10 1809, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.20348.5761 for Server 2022, 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.33650 for Server 2025, 10.0.26100.9711 for Windows 11 24H2, 10.0.26200.9711 for 25H2, 10.0.26300.9711 for 26H2, and 10.0.28000.3231 for 26H1 - as documented at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88116. Because exploitation is inferred to require the server to parse an attacker-influenced DNS response, the highest-value compensating controls are to disable recursion and forwarding on any DNS server that does not genuinely need to resolve external names (side effect: clients depending on that server as a resolver lose external name resolution and must be pointed at another resolver) and to restrict the server's ability to query untrusted upstream resolvers, allowing outbound DNS only to vetted forwarders (side effect: breaks resolution for internal zones that rely on open recursion). Additionally, block inbound UDP/TCP 53 from the public internet to DNS servers that only serve internal clients, segment DNS infrastructure so a compromised resolver cannot pivot laterally, and run the DNS service under a low-privilege account where operationally possible. Note that removing the DNS Server role entirely eliminates exposure for hosts that do not need it. No public exploit code was identified at time of analysis, so these measures are precautionary prioritization rather than a response to observed attacks.

Affected VersionsENISA

Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 16 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-822, Untrusted Pointer Dereference: the DNS service processes a pointer value that originates from attacker-influenced input - most plausibly fields within a DNS response that the server parses while acting as a recursive or forwarding resolver - and dereferences it without validating that it points to memory the process legitimately owns. In Windows DNS Server this class of bug typically surfaces in the DNS wire-format parsing path, where message compression pointers, record offsets, or resource-record lengths are decoded; a crafted response can steer the service into reading or writing through an attacker-chosen address, which in a service running with elevated privileges on the DNS host is the standard route from memory corruption to remote code execution. The CPE/version data in the EUVD record covers the entire current Windows DNS Server footprint - Windows Server 2016 (10.0.14393.x), Windows Server 2019 (10.0.17763.x), Windows Server 2022 (10.0.20348.x), Windows Server 2025 (10.0.26100.x, including Server Core), plus Windows 10 (1607/1809/21H2/22H2) and Windows 11 (23H2/24H2/25H2/26H1/26H2) client builds when the DNS Server role is enabled. The CVSS scope is Unchanged with High confidentiality, integrity, and availability impact, consistent with full code execution as the DNS service account rather than a mere denial of service; the accompanying intelligence tag "Authentication Bypass" should be read alongside the vector's PR:N, i.e. the attacker needs no credentials, and it does not add an independent access-control impact beyond what the vector already states.

Know when Windows 10 1607 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

Vendor (microsoft) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable DNS parsing flaw exploitable without credentials (AV:N/PR:N), but needs a triggering interaction (UI:R); memory-corruption RCE yields full C:H/I:H/A:H with no scope change.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:21 cve.org
HIGH 8.8

DescriptionCVE.org

Untrusted pointer dereference in DNS Server allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

A high-severity remote code execution flaw (CVE-2026-88116, CVSS 8.8) affects the Microsoft Windows DNS Server service on Windows Server 2016, 2019, 2022 and 2025 (including Server Core) as well as supported Windows 10/11 builds where the DNS Server role is installed. Successful exploitation would let an unauthenticated network attacker run code with the DNS service's privileges, putting the availability and integrity of name resolution - and any server hosting that role - at risk across the environment. Leadership should care because DNS is foundational infrastructure: compromise of a single DNS server can disrupt authentication, service discovery and internet-facing resolution for the entire organization.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 55% exploitable
Prevalence
High
Windows DNS Server role ubiquitous in enterprise Active Directory environments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy