Patch tracker / CVE reference / CVE-2026-35417

CVE-2026-35417

CVE-2026-35417 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. Its EPSS score puts the probability of exploitation in the next 30 days at 80%. Microsoft has shipped the fix: deploy one of the 13 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

80%

EPSS, 30 days

Critical

Severity

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

This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-35417

Third of the win32k escalations this cycle, rated Critical (CVSS 9.8) on Windows 10 Version 1809 and Windows Server 2019, with EPSS again at 72 percent. Three concurrent flaws in the win32k subsystem is a strong signal that a fuzzing or audit campaign hit paydirt, and public writeups on one variant tend to unlock the others. All are resolved by the same cumulative update.

Do this: Do not triage the win32k CVEs individually: confirm the single covering update is deployed fleet-wide and close all three at once.

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

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

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-35417 (source: https://senserva.com/cve/CVE-2026-35417.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-35417: Critical severity Microsoft vulnerability, CVSS 9.8
- EPSS 30-day exploitation probability: 80%
- Actively exploited (CISA KEV): no
- Fixed by: KB5087420, KB5087423, KB5087424, KB5087538, KB5087539, KB5087541, KB5087544, KB5087545, KB5089466, KB5089548, KB5089549, KB5093998, KB5094127
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.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 80%).

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

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2026-35417

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5087420, KB5087423, KB5087424, KB5087538, KB5087539, KB5087541, KB5087544, KB5087545, KB5089466, KB5089548, KB5089549, KB5093998, KB5094127 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-35417. 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 KB5087424 KB5087538 KB5087539 KB5087541 KB5087544 KB5087545 KB5089466 KB5089548 KB5089549 KB5093998 KB5094127

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-34348 CVE-2025-10263 CVE-2025-54518 CVE-2026-21530 CVE-2026-32161 CVE-2026-32170 CVE-2026-32209 CVE-2026-33828

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.