OTPulse

Role: DNS Server Information Disclosure Vulnerability

MonitorCVSS 6.5CVE-2026-108127Oct 13, 2026
Microsoft
IT in OT - Windows Server and Active Directory are widely deployed in OT environments
Attack path
Attack VectorNetwork
Auth RequiredLow
ComplexityLow
User InteractionNone needed
Summary

An out-of-bounds read vulnerability exists in the DNS Server component on Windows. An authorized attacker can send crafted DNS queries over the network to cause the DNS service to read and disclose memory contents. The vulnerability does not allow code execution or service disruption. Microsoft rates exploitation as "Less Likely" and has released updates for all supported Windows versions (10, 11, Server 2016, 2019, 2022, 2025).

What this means
What could happen
An attacker with DNS query access could read memory from the DNS server, potentially exposing sensitive information like IP addresses, hostnames, or other data stored in memory. This does not affect the DNS service itself but could compromise confidentiality of cached or in-transit data.
Who's at risk
Organizations running Windows Server 2016, 2019, 2022, or 2025 as DNS servers should prioritize patching. This also affects Windows 10 and Windows 11 systems if they are operating as DNS servers. Water utilities and electric utilities managing their own DNS infrastructure should ensure all authoritative DNS servers and domain controllers (which run DNS) are updated. Small IT shops that have Windows servers handling DNS are at risk.
How it could be exploited
An attacker sends specially crafted DNS queries over the network to a Windows DNS Server. The out-of-bounds read vulnerability allows the attacker to read portions of server memory that are returned in DNS responses, disclosing information an attacker should not access.
Prerequisites
  • Network access to DNS port 53 on a Windows DNS Server
  • Valid domain user credentials or ability to query the DNS server
remotely exploitablerequires valid credentials or authorized DNS accessinformation disclosure only (no code execution)affects all supported Windows DNS servers
Exploitability
Unlikely to be exploited — EPSS score 0.9%
Affected products (28)
28 with fix
ProductAffected VersionsFix Status
Windows 10 Version 1607 for 32-bit SystemsAll versionsBuild 10.0.14393.9612
Windows 10 Version 1607 for x64-based SystemsAll versionsBuild 10.0.14393.9612
Windows Server 2016All versionsBuild 10.0.14393.9612
Windows Server 2016 (Server Core installation)All versionsBuild 10.0.14393.9612
Windows 10 Version 1809 for 32-bit SystemsAll versionsBuild 10.0.17763.9376
Remediation & Mitigation
0/9
Do now
0/1
WORKAROUNDRestrict DNS port 53 (TCP and UDP) access to DNS servers from only authorized DNS clients and resolvers using firewall rules
Schedule — requires maintenance window
0/8

Patching may require device reboot — plan for process interruption

Windows Server 2016
HOTFIXUpdate Windows Server 2016 systems to Build 10.0.14393.9612 or later
Windows Server 2019
HOTFIXUpdate Windows Server 2019 systems to Build 10.0.17763.9376 or later
Windows Server 2022
HOTFIXUpdate Windows Server 2022 systems to Build 10.0.20348.5761 or later
Windows Server 2025
HOTFIXUpdate Windows Server 2025 systems to Build 10.0.26100.33650 or later
All products
HOTFIXUpdate Windows 10 Version 1607 systems to Build 10.0.14393.9612 or later
HOTFIXUpdate Windows 10 Version 1809 systems to Build 10.0.17763.9376 or later
HOTFIXUpdate Windows 10 Version 21H2 and 22H2 systems to Build 10.0.19044.7807 or later
HOTFIXUpdate Windows 11 systems to the appropriate build: 23H2 to Build 10.0.22631.7652, 24H2 to Build 10.0.26100.9711, 25H2 to Build 10.0.26200.9711, 26H2 to Build 10.0.26300.9711, or 26H1 to Build 10.0.28000.3231
View full vendor advisory
API: /api/v1/advisories/198413a9-6e91-4839-b1b8-f5401dc07b4c

Get OTPulse briefings by email

Advisory breakdowns and incident analyses for the people actually defending OT environments. Sent when there's something worth your attention, not on a schedule. Free, no account required.