Patch tracker / CVE reference / CVE-2026-41096

CVE-2026-41096

CVE-2026-41096 is a Microsoft vulnerability that Microsoft rates Critical, with a CVSS score of 9.8 (Critical). Microsoft has shipped the fix: deploy one of the 8 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Critical

9.8

CVSS v3

2.3%

EPSS, 30 days

Critical

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.3%. CVSS 9.8 (Critical).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-41096

CVE-2026-41096 is a Critical remote code execution flaw (CVSS 9.8) in the Windows DNS Client, meaning a malicious DNS response could execute code on systems that make name lookups. Exposed systems include Windows Server 2025 Server Core and Windows 11 25H2 on both ARM64 and x64. It is not in CISA KEV and not tied to ransomware yet, but the 80 percent EPSS score signals exploitation is likely soon, and the DNS Client runs on essentially every affected host.

Do this: Deploy Microsoft's patch for CVE-2026-41096 to all Windows Server 2025 Server Core and Windows 11 25H2 (ARM64 and x64) systems, prioritizing internet-facing and DNS-dependent servers first.

AI-generated from public data, 2026-07-26. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-41096

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-41096 (source: https://senserva.com/cve/CVE-2026-41096.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2026-41096: Microsoft vulnerability, Microsoft rating Critical, CVSS 9.8 (Critical)
- EPSS 30-day exploitation probability: 2.3%
- Actively exploited (CISA KEV): no
- Fixed by: KB5087420, KB5087423, KB5087539, KB5087541, KB5089466, KB5089548, KB5089549, KB5093998
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed as of 2026-10-14: not in the CISA KEV catalog, EPSS 2%.

Fixed by KB5087420 and 7 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-41096

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5087420, KB5087423, KB5087539, KB5087541, KB5089466, KB5089548, KB5089549, KB5093998 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-41096. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5087420 KB5087423 KB5087539 KB5087541 KB5089466 KB5089548 KB5089549 KB5093998

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-54518 CVE-2026-41089 CVE-2026-44815 CVE-2026-45657 CVE-2026-47291 CVE-2026-42904 CVE-2025-10263 CVE-2026-40402

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.