CVE-2026-65789 json
Windows DNS Server Remote Code Execution Vulnerability
published 3mo ago modified yesterday also EUVD-2026-56442
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Use after free in Windows DNS allows an unauthorized attacker to execute code over a network.
Patch / fix
- Microsoft Windows Server 2016 10.0.14393.9418
- Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.9418
- Microsoft Windows Server 2019 10.0.17763.9121
- Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.9121
- Microsoft Windows Server 2022 10.0.20348.5499
- Microsoft Windows Server 2025 10.0.26100.33296
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.33296
Is CVE-2026-65789 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Windows Server 2016
- Microsoft Windows Server 2016 (Server Core installation)
- Microsoft Windows Server 2019
- Microsoft Windows Server 2019 (Server Core installation)
- Microsoft Windows Server 2022
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-65789
vendor-advisory, patch
Sources
- CVE List CVE-2026-65789
- NVD CVE-2026-65789
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.