CVE-2026-96176 json
Windows DNS Denial of Service Vulnerability
published yesterday modified 17h ago also EUVD-2026-121498
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Missing release of memory after effective lifetime in Windows DNS allows an unauthorized attacker to deny service over a network.
Patch / fix
- Microsoft Windows 11 version 23H2 10.0.22631.7711
- Microsoft Windows 11 Version 24H2 10.0.26100.9974
- Microsoft Windows 11 Version 25H2 10.0.26200.9974
- Microsoft Windows 11 version 26H1 10.0.28000.3501
- Microsoft Windows 11 Version 26H2 10.0.26300.9974
- Microsoft Windows Server 2025 10.0.26100.33822
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.33822
Is CVE-2026-96176 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
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Microsoft Windows 11 version 23H2
- Microsoft Windows 11 Version 24H2
- Microsoft Windows 11 Version 25H2
- Microsoft Windows 11 version 26H1
- Microsoft Windows 11 Version 26H2
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-96176
vendor-advisory, patch
Sources
- CVE List CVE-2026-96176
- NVD CVE-2026-96176
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.