Patch tracker / KB5087053
KB5087053: .NET 8.0 installed on Windows Security Update (May 2026)
KB5087053 is a High security update for .NET 8.0 installed on Windows, released 2026-05-12. It closes 2 CVEs with a maximum CVSS of 7.3. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.
Microsoft security update released 2026-05-12. Fixes 2 CVEs.
No exploitation is confirmed for the CVEs in this update and the EPSS exploitation probability is currently <1%. That can change: CVEs from past updates regularly get exploited months later, which is why deploying on your normal cadence, without exceptions that linger, is what keeps this one boring.
Most organizations deliver an update like this automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; the install section below covers each path. For the bigger picture: how the Microsoft patching tools fit together, this month's Patch Tuesday summary, and every update ranked by real-world risk.
Updated July 25, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Download KB5087053
Get the official update for KB5087053. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5087053
KB5087053 patches two CVEs across .NET 8.0, 9.0, and 10.0 on Windows, with the more serious rated High at CVSS 7.3. Anyone running .NET applications or hosting .NET workloads on these runtime versions is exposed, though EPSS sits at only 1% and neither CVE is in CISA KEV or linked to ransomware. The spread across three supported .NET generations means most Windows estates with .NET installed will need this rather than a niche subset.
Do this: Inventory which .NET 8.0, 9.0, and 10.0 runtimes and SDKs are installed on your Windows servers and workstations, then deploy KB5087053 to those hosts.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5087053
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5087053
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Exploitation and severity
Fixes 2 CVEs. Most severe CVSS 7.3 (High). EPSS exploit probability up to <1%.
Among the lower half of tracked Microsoft updates by EPSS exploit probability.
What to do
Moderate priority: schedule it in your normal patch cycle. Senserva flags whether KB5087053 is missing on your devices.
Check if KB5087053 is installed
Copy-paste PowerShell: one machine, or your whole fleet in one pass. No output means the update is not installed.
Get-HotFix covers Windows updates. Office, SharePoint, and Exchange server updates show under installed updates in Programs and Features, or check the Update Catalog history.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5087053 (checked 2026-07-22). Verify against the article before acting.
Microsoft is not currently aware of any issues in this update.
Writing about KB5087053? Cite this page
Copy-paste for a blog post, forum answer, or internal doc. The link always carries the current risk data.
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2026-32177 | High | 7.5 | 2.4% | No |
| CVE-2026-35433 | High | 7.5 | 2.4% | No |
Affected products
Also released in May 2026
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5087053
Any of these paths delivers KB5087053; most organizations already have one of the first three running:
- Intune update rings (Windows Update for Business): the update flows on each ring's deferral schedule.
- Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
- WSUS / Configuration Manager: approve KB5087053 for your device groups and set a deadline.
- Manual: download from the Update Catalog above and install; fine for a handful of machines, unmanageable at any real scale.
After the rollout, verify rather than assume: update compliance reporting in Intune or Autopatch shows which devices actually installed it, and Siemserva reads Intune, Defender, Autopatch, and Azure Update Manager together to show the devices still missing KB5087053, ranked by exploitation.
Common questions about KB5087053
Does KB5087053 have known issues?
Yes. Microsoft's support article documents known issues for KB5087053 (checked 2026-07-22). The Known issues section on this page quotes it; verify against the article before acting.
Is KB5087053 urgent?
KB5087053 is rated High. Include it in your normal patch cycle unless your environment raises its priority.
How do I download KB5087053?
From the Microsoft Update Catalog (linked on this page), or let Intune, Windows Update for Business, Windows Autopatch, or WSUS deliver it. The catalog page lists the download for each supported product.
How do I deploy KB5087053 with Intune?
Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. For urgent updates, Intune expedite policies can bypass the ring deferrals. Verify the rollout with update compliance reporting rather than assuming delivery.
Can I ask my own AI about KB5087053?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5087053's key facts: severity, CVE count, exploitation status, and the download link. Copy it into Claude, ChatGPT, or Copilot for a rollout plan; the data is refreshed twice a day (5 AM and 3 PM US Central).
Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.
