Skip to content
major vulnerability· requires attention

Core Microsoft Windows DNS component affected; network remote privilege escalation in a ubiquitous OS can impact many organizations and warrants broad IT notice.

Systems

CVE-2026-62778

8.1
High
EPSS 0.51%Patch availableAug 12, 2026

Windows DNS use-after-free allows remote privilege escalation

common questions

Is CVE-2026-62778 being exploited?

Not confirmed. CVE-2026-62778 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-62778?

CVE-2026-62778 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62778?

Yes. A fix has been recorded for CVE-2026-62778. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62778 affect?

CVE-2026-62778 affects Microsoft Windows DNS service (client and server DNS components). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62778?

Apply vendor patch immediately; if unavailable, restrict DNS service access and firewall DNS traffic.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Microsoft Windows DNS service (client and server DNS components)
impact

Remote attackers can exploit a DNS use-after-free to elevate privileges (potentially to SYSTEM) over the network.

action required

Immediate action required

affected versions
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.9418
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.9121
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.26280
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.23338
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.23338
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.26280
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.9418
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.9418
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9121
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9121
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5499
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33296
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33296

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free