Vulnerability in Microsoft Windows DNS component; widespread OS impact that can disrupt enterprise infrastructure if exploited.
CVE-2026-65789
Windows DNS use-after-free allows remote code execution over the network.
Is CVE-2026-65789 being exploited?
Not confirmed. CVE-2026-65789 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.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-65789?
CVE-2026-65789 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-65789?
Yes. A fix has been recorded for CVE-2026-65789. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65789 affect?
CVE-2026-65789 affects Microsoft Windows DNS component, Windows Server (DNS role), Windows DNS resolver/service. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65789?
Apply vendor patch when available; restrict DNS exposure and monitor affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via use-after-free in Windows DNS, enabling attackers to run arbitrary code on vulnerable hosts over the network.
Immediate action required
- affected>= 10.0.14393.0 and < 10.0.14393.9418
- affected>= 10.0.14393.0 and < 10.0.14393.9418
- affected>= 10.0.17763.0 and < 10.0.17763.9121
- affected>= 10.0.17763.0 and < 10.0.17763.9121
- affected>= 10.0.20348.0 and < 10.0.20348.5499
- affected>= 10.0.26100.0 and < 10.0.26100.33296
- 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.