CVE-2026-88129: Microsoft DNS Server out-of-bounds read

CVE-2026-88129 · Severity: medium · CVSS 6.5 · Published 2026-10-13

A flaw in Microsoft's DNS Server allows an authorized attacker to cause it to crash or stop responding to legitimate requests, disrupting DNS name resolution for networks that depend on it. This requires the attacker to already have valid credentials or network access to the DNS service. An outage could prevent users from accessing websites and cloud services by name.

Technologies: Microsoft DNS Server, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2025. Vendors: Microsoft.

Quick answers

Is CVE-2026-88129 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-88129 being exploited in the wild.
How severe is CVE-2026-88129?
Medium severity, with a CVSS score of 6.5, published 13 October 2026.
Which products and versions are affected?
Microsoft DNS Server.
Is there a fix for CVE-2026-88129?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-88129 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-88129?
Check whether you run Microsoft DNS Server, Microsoft Windows Server 2012, Microsoft Windows Server 2016 or one of the others listed. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds read vulnerability in the DNS Server component allows an authenticated network attacker to trigger a denial of service condition. The vulnerability requires prior network access or authentication to the DNS service; exploitation causes the service to crash or become unresponsive, disrupting DNS resolution for affected networks. A fix is available from Microsoft.

Affected products

  • Microsoft DNS Server

Timeline

  • 2026-10-13: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.