Patch tracker / KB5089548
KB5089548: Windows Server 2019 Security Update (July 2026)
KB5089548 is a Critical security update for Windows Server 2019, released 2026-07-14. It closes 62 CVEs with a maximum CVSS of 9.8. 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-07-14. Fixes 62 CVEs.
No exploitation is confirmed for the CVEs in this update and the EPSS exploitation probability is currently 4.7%. 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 23, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Download KB5089548
Get the official update for KB5089548. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5089548
KB5089548 is the July 2026 security update for Windows 11 Version 26H1 on ARM64 hardware, a narrow platform slice that covers Surface Pro X style devices and other ARM laptops rather than mainstream x64 fleets. The per-update CVE detail is still provisional, so treat this as part of a large cycle carrying 622 CVEs and 56 rated Critical across all updates, with no named zero-day mapped to this specific package. ARM64 builds are often patched and tested later than x64, so admins may not have this in their usual ring.
Do this: Confirm your ARM64 Windows 11 26H1 devices are enrolled in patch scanning and stage KB5089548 to a pilot ring now, then revisit the CVE list once Microsoft publishes final detail.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5089548
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5089548
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 62 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 4.7%.
Among the top half of tracked Microsoft updates by EPSS exploit probability.
What to do
Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. Senserva flags whether KB5089548 is missing on your devices.
Check if KB5089548 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 KB5089548 (checked 2026-07-21). Verify against the article before acting.
Microsoft is not currently aware of any issues with this update.
Writing about KB5089548? 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-34348 | Critical | 9.9 | 7.5% | No |
| CVE-2025-54518 | Critical | 9.8 | 72% | No |
| CVE-2026-21530 | Critical | 9.8 | 72% | No |
| CVE-2026-32161 | Critical | 9.8 | 72% | No |
| CVE-2026-32170 | Critical | 9.8 | 72% | No |
| CVE-2026-32209 | Critical | 9.8 | 72% | No |
| CVE-2026-33834 | Critical | 9.8 | 72% | No |
| CVE-2026-33835 | Critical | 9.8 | 72% | No |
| CVE-2026-33837 | Critical | 9.8 | 72% | No |
| CVE-2026-33838 | Critical | 9.8 | 72% | No |
| CVE-2026-33839 | Critical | 9.8 | 72% | No |
| CVE-2026-33840 | Critical | 9.8 | 72% | No |
| CVE-2026-33841 | Critical | 9.8 | 72% | No |
| CVE-2026-34329 | Critical | 9.8 | 72% | No |
| CVE-2026-34330 | Critical | 9.8 | 72% | No |
| CVE-2026-34331 | Critical | 9.8 | 72% | No |
| CVE-2026-34333 | Critical | 9.8 | 72% | No |
| CVE-2026-34334 | Critical | 9.8 | 72% | No |
| CVE-2026-34336 | Critical | 9.8 | 72% | No |
| CVE-2026-34337 | Critical | 9.8 | 72% | No |
| CVE-2026-34338 | Critical | 9.8 | 72% | No |
| CVE-2026-34339 | Critical | 9.8 | 72% | No |
| CVE-2026-34340 | Critical | 9.8 | 72% | No |
| CVE-2026-34341 | Critical | 9.8 | 72% | No |
| CVE-2026-34342 | Critical | 9.8 | 72% | No |
| CVE-2026-34343 | Critical | 9.8 | 72% | No |
| CVE-2026-34344 | Critical | 9.8 | 72% | No |
| CVE-2026-34345 | Critical | 9.8 | 72% | No |
| CVE-2026-34347 | Critical | 9.8 | 72% | No |
| CVE-2026-34351 | Critical | 9.8 | 72% | No |
| CVE-2026-35415 | Critical | 9.8 | 72% | No |
| CVE-2026-35416 | Critical | 9.8 | 72% | No |
| CVE-2026-35417 | Critical | 9.8 | 72% | No |
| CVE-2026-35418 | Critical | 9.8 | 72% | No |
| CVE-2026-35419 | Critical | 9.8 | 72% | No |
| CVE-2026-35421 | Critical | 9.8 | 72% | No |
| CVE-2026-35422 | Critical | 9.8 | 72% | No |
| CVE-2026-35423 | Critical | 9.8 | 72% | No |
| CVE-2026-35424 | Critical | 9.8 | 72% | No |
| CVE-2026-40369 | Critical | 9.8 | 72% | No |
| CVE-2026-40377 | Critical | 9.8 | 72% | No |
| CVE-2026-40380 | Critical | 9.8 | 72% | No |
| CVE-2026-40382 | Critical | 9.8 | 72% | No |
| CVE-2026-40397 | Critical | 9.8 | 72% | No |
| CVE-2026-40398 | Critical | 9.8 | 72% | No |
| CVE-2026-40399 | Critical | 9.8 | 72% | No |
| CVE-2026-40401 | Critical | 9.8 | 72% | No |
| CVE-2026-40403 | Critical | 9.8 | 72% | No |
| CVE-2026-40405 | Critical | 9.8 | 72% | No |
| CVE-2026-40406 | Critical | 9.8 | 72% | No |
| CVE-2026-40407 | Critical | 9.8 | 72% | No |
| CVE-2026-40408 | Critical | 9.8 | 72% | No |
| CVE-2026-40410 | Critical | 9.8 | 72% | No |
| CVE-2026-40413 | Critical | 9.8 | 72% | No |
| CVE-2026-40414 | Critical | 9.8 | 72% | No |
| CVE-2026-40415 | Critical | 9.8 | 72% | No |
| CVE-2026-41088 | Critical | 9.8 | 72% | No |
| CVE-2026-41096 | Critical | 9.8 | 72% | No |
| CVE-2026-41097 | Critical | 9.8 | 72% | No |
| CVE-2026-42825 | Critical | 9.8 | 72% | No |
| CVE-2026-42896 | Critical | 9.8 | 72% | No |
| CVE-2026-48566 | Critical | 9.8 | 72% | No |
Affected products
Also released in July 2026
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5089548
Any of these paths delivers KB5089548; 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 KB5089548 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 KB5089548, ranked by exploitation.
Common questions about KB5089548
Does KB5089548 have known issues?
Yes. Microsoft's support article documents known issues for KB5089548 (checked 2026-07-21). The Known issues section on this page quotes it; verify against the article before acting.
Is KB5089548 urgent?
KB5089548 is rated Critical with a maximum CVSS of 9.8. No active exploitation is confirmed yet, so schedule it in your prompt patch cycle.
How do I download KB5089548?
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 KB5089548 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 KB5089548?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5089548'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 three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.
