According to MSRC's official description, an out-of-bounds read in Windows DNS allows an unauthorized attacker to disclose information over a network. While that summary sounds ominous for any infrastructure team running internal or external name resolution, the fine print in Microsoft's advisory offers immediate relief for administrators running standard configurations—along with a clear mandate to patch across four generations of Windows Server.
CVE-2026-108425 Advisory Breakdown and Risk Metrics
Before scheduling maintenance windows, IT teams need the exact telemetry from Microsoft's official security update guide to feed into vulnerability management trackers and risk matrices. Here is the complete breakdown for CVE-2026-108425:
- CVE ID: CVE-2026-108425
- Vulnerability Title: Windows DNS Information Disclosure Vulnerability
- Severity: Important
- CVSS Base Score: 5.9
- CVSS Temporal Score: 5.2
- CVSS Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C - Weakness Classification: CWE-125
- Exploitation Assessment: Exploitation Less Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
Looking closely at the CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C), several practical traits stand out from general security engineering analysis. The attack vector is network-based (AV:N), requires zero privileges (PR:N), and demands no user interaction (UI:N). Furthermore, integrity (I:N) and availability (A:N) are unaffected; this bug will not directly modify DNS zones or crash the service on its own, though confidentiality impact is rated high (C:H).
Why, then, does the base score sit at a moderate 5.9 alongside an MSRC assessment of Exploitation Less Likely? The answer lies squarely in the high attack complexity (AC:H) metric.
Section Summary: CVE-2026-108425 is an Important-severity CWE-125 flaw with neither public disclosure nor active exploitation reported, though administrators still must take action to remediate affected servers.
The Debug Logging Catch: How the Vulnerability Works
Memory safety bugs like CWE-125 (out-of-bounds read) occur when software reads data past the end—or before the beginning—of an intended memory buffer. In a network daemon that parses untrusted packets all day, reading past a buffer boundary can sweep up adjacent heap or process memory and reflect or expose that data back to an unauthorized requester.
Microsoft's official advisory facts clarify both the exposure scope and the exact precondition required to trigger the bug:
- Information Exposed: When addressing what type of information could be disclosed by this vulnerability, MSRC states that an attacker who successfully exploited this vulnerability could read memory from the affected DNS Server service.
- Attack Complexity Precondition: Addressing why attack complexity is high (
AC:H) according to the CVSS metric, MSRC confirms that successful exploitation requires DNS packet debug logging to be enabled on the affected server, noting that this logging is disabled by default. - Core Advisory Mechanism: Windows DNS Information Disclosure Vulnerability: Out-of-bounds read in Windows DNS allows an unauthorized attacker to disclose information over a network.
From an operational standpoint—synthesizing general industry knowledge of Windows DNS administration—this precondition is a classic "troubleshooting hangover." Administrators routinely enable DNS packet debug logging when hunting down malformed queries, split-brain resolution hiccups, or chatty clients hammering domain controllers. Because DNS packet debug logging is disabled by default, freshly deployed and standard-configuration servers are insulated from exploitation out of the box. However, in sprawling enterprise environments where diagnostic toggles are enabled during an incident and forgotten for months, those exact servers suddenly sit inside the blast radius.
And why should defenders care about someone reading memory from the affected DNS Server service? Even without direct code execution (I:N, A:N), leaking process memory from a core infrastructure service can hand an attacker memory layout pointers, cached query artifacts, or internal state details that make subsequent lateral movement or chained attacks far easier to pull off.
Section Summary: An attacker cannot trigger this CWE-125 memory leak against a default installation; DNS packet debug logging must be explicitly enabled for an unauthorized network attacker to read memory from the DNS Server service.
Affected Products, KB Updates, and Fixed Builds
This vulnerability spans both full Desktop Experience and Server Core x64 editions across four server generations. Notably, Windows Server 2025 (x64) and Windows Server 2025 (Server Core installation) (x64) have two distinct KB-to-build update paths documented by Microsoft.
| Affected Product | KB Article | Fixed Build |
|---|---|---|
| Windows Server 2016 (Server Core installation) (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2016 (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2019 (Server Core installation) (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2019 (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2022 (Server Core installation) (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2022 (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2025 (Server Core installation) (x64) | KB5131077 | 10.0.26100.33730 |
| Windows Server 2025 (Server Core installation) (x64) | KB5131080 | 10.0.26100.33822 |
| Windows Server 2025 (x64) | KB5131077 | 10.0.26100.33730 |
| Windows Server 2025 (x64) | KB5131080 | 10.0.26100.33822 |
Exact Official Remediation Guidance
To ensure compliance scanners and patch runbooks match Microsoft's security update release exactly, apply the corresponding updates as specified for each platform:
- For Windows Server 2016 (Server Core installation) (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2016 (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2019 (Server Core installation) (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2019 (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2022 (Server Core installation) (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2022 (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2025 (Server Core installation) (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
- For Windows Server 2025 (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
Section Summary: Microsoft has shipped official security updates across every affected server release—KB5131291, KB5131085, KB5131090, KB5131077, and KB5131080—giving administrators clear build numbers to verify patch completion.
Practical Hardening and Rollout Strategy for Sysadmins
How urgently should you wake up the change-advisory board? Let's weigh both sides objectively based on the evidence and standard enterprise patch operations.
On one hand, there is no reason to panic-reboot primary DNS servers in the middle of peak business hours. With Publicly disclosed: No, Exploited: No, an assessment of Exploitation Less Likely, and the requirement that DNS packet debug logging be turned on, default deployments face minimal immediate exposure. On the other hand, treating AC:H vulnerabilities as permanent low priorities is a trap. Diagnostic packet logging gets toggled on precisely when networks are misbehaving—or worse, during active security investigations when defenders want deeper visibility into suspicious name queries. Leaving a DNS server unpatched means turning on packet debug logging during a future incident could inadvertently open a memory disclosure hole right when an adversary is already probing your network.
Follow a clean, three-step operational workflow to close CVE-2026-108425:
- Audit DNS Packet Debug Logging Immediately: Check your DNS fleet to see whether any server currently has DNS packet debug logging enabled from past troubleshooting sessions. Turning unnecessary packet debug logging back to its default disabled state immediately removes the precondition needed for exploitation while you stage OS updates.
- Stage and Roll Out Cumulative Security Updates: Sequence reboots across redundant DNS servers so name resolution stays uninterrupted. Prioritize internet-facing authoritative DNS hosts and DMZ forwarders first, followed by internal Active Directory-integrated DNS servers across
Windows Server 2016 (x64),Windows Server 2019 (x64),Windows Server 2022 (x64),Windows Server 2025 (x64), and their respective(Server Core installation) (x64)counterparts. - Verify Target Builds Post-Reboot: Confirm that each patched machine reports the exact fixed OS build—
10.0.14393.9688,10.0.17763.9487,10.0.20348.5870,10.0.26100.33730, or10.0.26100.33822—before signing off on your patch cycle.
If you are coordinating a broader server maintenance window or sharing patch notes with fellow admins, check out our ongoing Windows Server security patch discussions and Active Directory infrastructure threads right here on WindowsForum.com. Keeping debug switches off when you don't need them—and keeping your DNS builds current—remains one of the simplest ways to ensure your network's phonebook doesn't start reading its own private diary out loud.
References
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com