CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVE-2026-96064 Windows Domain Name Service Remote Code Execution Vulnerability
High (8.8) in microsoft. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
On this page
Heap-based buffer overflow in DNS Server allows an authorized attacker to execute code over a network.
Severity
- EPSS
- 0.7% estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-122 Heap-based Buffer Overflow
- Published
- Modified
- Assigned by
- microsoft (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-96064 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96064?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96064?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96064 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-96064)
HTML:
<a href="https://cve.bz/cve/CVE-2026-96064"><img src="https://cve.bz/cve/badge/CVE-2026-96064.svg" alt="CVE-2026-96064"></a>
Affected
- 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)
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft Windows Server 2016 | from 10.0.14393.0 before 10.0.14393.9688 |
| Microsoft Windows Server 2016 (Server Core installation) | from 10.0.14393.0 before 10.0.14393.9688 |
| Microsoft Windows Server 2019 | from 10.0.17763.0 before 10.0.17763.9487 |
| Microsoft Windows Server 2019 (Server Core installation) | from 10.0.17763.0 before 10.0.17763.9487 |
| Microsoft Windows Server 2022 | from 10.0.20348.0 before 10.0.20348.5870 |
| Microsoft Windows Server 2025 | from 10.0.26100.0 before 10.0.26100.33822 |
| Microsoft Windows Server 2025 (Server Core installation) | from 10.0.26100.0 before 10.0.26100.33822 |
Attack patterns (CAPEC)
- CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.