Patch tracker / KB5093998
KB5093998: Windows Server 2019 Security Update (June 2026)
Updated July 21, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Hot patch: #3 hottest Microsoft update right now, a must-install (as of 2026-07-21)Microsoft security update released 2026-06-09. Fixes 158 CVEs.
All about KB5093998: the download, the Senserva AI read, known issues from Microsoft, what the press says about it, a PowerShell installed-check, install guidance, the CVEs it fixes, and its change history.
KB5093998 is a Critical security update for Windows Server 2019, released 2026-06-09. It closes 158 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.
No exploitation is confirmed yet, but the EPSS model puts the 30-day exploitation probability for the worst CVE here at 48%, which is high enough to treat this as more urgent than its Critical label alone suggests. Attackers reverse-engineer Patch Tuesday updates within days, so the safe assumption is that exploit code follows the patch.
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.
Download KB5093998
Get the official update for KB5093998. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5093998
KB5093998 is a large Windows 10 1809 and Server 2019 rollup fixing 158 CVEs, with the worst rated Critical at CVSS 9.8 and a top EPSS of 48 percent, which is high for something not yet in the CISA KEV catalog. Anyone still running the aging 1809 branch or Server 2019 is exposed, and the 48 percent exploit-prediction score means at least one of these flaws is a realistic near-term target even without confirmed exploitation.
Do this: Schedule and deploy KB5093998 to all Windows 10 1809 and Server 2019 systems this cycle, prioritizing the Critical CVSS 9.8 issue and any internet-facing Server 2019 hosts.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5093998
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5093998
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 158 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 48%.
Among the top 25% 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 KB5093998 is missing on your devices.
Check if KB5093998 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 KB5093998 (checked 2026-07-21). Verify against the article before acting.
Microsoft Office applications might fail to open from certain third-party apps
Symptoms
Microsoft has received reports of an issue in which certain third-party applications might be unable to launch Microsoft Office applications or open documents after installing the Windows updates released on or after June 9, 2026. This issue affects certain third-party applications that use OLE automation to interact with Microsoft Office applications. In some cases, the Office application or document might fail to open without displaying an error message.
Affected Microsoft Office applications might include Word, Excel, PowerPoint, Access, and other Microsoft Office applications when launched from within the affected third-party application.
Reports indicate that this issue may affect applications such as CCH Engagement, Workpaper Manager, dental software (such as Dentrix and Softdent), and Zotero; other similar applications might also be impacted.
Third-party information disclaimer
The third-party products listed are manufactured by companies that are independent of Microsoft. We make no warranty, implied or otherwise, about the performance or reliability of these products.
Workaround
This issue is resolved in Windows updates released on and after July 14, 2026 such as KB5099414 . We recommend you install the latest Windows update for your device as it contains important improvements and ...
Writing about KB5093998? 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-2025-10263 | Critical | 9.8 | 48% | 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-33828 | Critical | 9.8 | 48% | 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-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-34335 | Critical | 9.8 | 48% | 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-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-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-40402 | Critical | 9.8 | 72% | No |
| CVE-2026-40403 | Critical | 9.8 | 72% | No |
| CVE-2026-40404 | Critical | 9.8 | 48% | 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-40409 | Critical | 9.8 | 48% | 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-41092 | Critical | 9.8 | 48% | No |
| CVE-2026-41096 | Critical | 9.8 | 72% | No |
| CVE-2026-41097 | Critical | 9.8 | 72% | No |
| CVE-2026-41108 | Critical | 9.8 | 48% | No |
| CVE-2026-42825 | Critical | 9.8 | 72% | No |
| CVE-2026-42828 | Critical | 9.8 | 48% | No |
| CVE-2026-42836 | Critical | 9.8 | 48% | No |
| CVE-2026-42837 | Critical | 9.8 | 48% | No |
| CVE-2026-42903 | Critical | 9.8 | 48% | No |
| CVE-2026-42904 | Critical | 9.8 | 48% | No |
| CVE-2026-42905 | Critical | 9.8 | 48% | No |
| CVE-2026-42906 | Critical | 9.8 | 48% | No |
| CVE-2026-42907 | Critical | 9.8 | 48% | No |
| CVE-2026-42908 | Critical | 9.8 | 48% | No |
| CVE-2026-42909 | Critical | 9.8 | 48% | No |
| CVE-2026-42911 | Critical | 9.8 | 48% | No |
| CVE-2026-42912 | Critical | 9.8 | 48% | No |
| CVE-2026-42913 | Critical | 9.8 | 48% | No |
| CVE-2026-42914 | Critical | 9.8 | 48% | No |
| CVE-2026-42915 | Critical | 9.8 | 48% | No |
| CVE-2026-42916 | Critical | 9.8 | 48% | No |
| CVE-2026-42968 | Critical | 9.8 | 48% | No |
| CVE-2026-42969 | Critical | 9.8 | 48% | No |
| CVE-2026-42970 | Critical | 9.8 | 48% | No |
| CVE-2026-42971 | Critical | 9.8 | 48% | No |
| CVE-2026-42972 | Critical | 9.8 | 48% | No |
| CVE-2026-42973 | Critical | 9.8 | 48% | No |
| CVE-2026-42974 | Critical | 9.8 | 48% | No |
| CVE-2026-42977 | Critical | 9.8 | 48% | No |
| CVE-2026-42978 | Critical | 9.8 | 48% | No |
| CVE-2026-42979 | Critical | 9.8 | 48% | No |
| CVE-2026-42980 | Critical | 9.8 | 48% | No |
| CVE-2026-42981 | Critical | 9.8 | 48% | No |
| CVE-2026-42983 | Critical | 9.8 | 48% | No |
| CVE-2026-42984 | Critical | 9.8 | 48% | No |
| CVE-2026-42985 | Critical | 9.8 | 48% | No |
| CVE-2026-42986 | Critical | 9.8 | 48% | No |
| CVE-2026-42989 | Critical | 9.8 | 48% | No |
| CVE-2026-42991 | Critical | 9.8 | 48% | No |
| CVE-2026-42992 | Critical | 9.8 | 48% | No |
| CVE-2026-42993 | Critical | 9.8 | 48% | No |
| CVE-2026-44799 | Critical | 9.8 | 48% | No |
| CVE-2026-44801 | Critical | 9.8 | 48% | No |
| CVE-2026-44802 | Critical | 9.8 | 48% | No |
| CVE-2026-44803 | Critical | 9.8 | 48% | No |
| CVE-2026-44810 | Critical | 9.8 | 48% | No |
| CVE-2026-44812 | Critical | 9.8 | 48% | No |
| CVE-2026-44815 | Critical | 9.8 | 48% | No |
| CVE-2026-45487 | Critical | 9.8 | 48% | No |
| CVE-2026-45586 | Critical | 9.8 | 48% | No |
| CVE-2026-45588 | Critical | 9.8 | 48% | No |
| CVE-2026-45592 | Critical | 9.8 | 48% | No |
| CVE-2026-45593 | Critical | 9.8 | 48% | No |
| CVE-2026-45594 | Critical | 9.8 | 48% | No |
| CVE-2026-45595 | Critical | 9.8 | 48% | No |
| CVE-2026-45596 | Critical | 9.8 | 48% | No |
| CVE-2026-45597 | Critical | 9.8 | 48% | No |
| CVE-2026-45598 | Critical | 9.8 | 48% | No |
| CVE-2026-45599 | Critical | 9.8 | 48% | No |
| CVE-2026-45601 | Critical | 9.8 | 48% | No |
| CVE-2026-45602 | Critical | 9.8 | 48% | No |
| CVE-2026-45603 | Critical | 9.8 | 48% | No |
| CVE-2026-45604 | Critical | 9.8 | 48% | No |
| CVE-2026-45605 | Critical | 9.8 | 48% | No |
| CVE-2026-45606 | Critical | 9.8 | 48% | No |
| CVE-2026-45607 | Critical | 9.8 | 48% | No |
| CVE-2026-45608 | Critical | 9.8 | 48% | No |
| CVE-2026-45634 | Critical | 9.8 | 48% | No |
| CVE-2026-45635 | Critical | 9.8 | 48% | No |
| CVE-2026-45636 | Critical | 9.8 | 48% | No |
| CVE-2026-45637 | Critical | 9.8 | 48% | No |
| CVE-2026-45638 | Critical | 9.8 | 48% | No |
| CVE-2026-45639 | Critical | 9.8 | 48% | No |
| CVE-2026-45640 | Critical | 9.8 | 48% | No |
| CVE-2026-45641 | Critical | 9.8 | 48% | No |
| CVE-2026-45642 | Critical | 9.8 | 48% | No |
| CVE-2026-45653 | Critical | 9.8 | 48% | No |
| CVE-2026-45655 | Critical | 9.8 | 48% | No |
| CVE-2026-45656 | Critical | 9.8 | 48% | No |
| CVE-2026-45657 | Critical | 9.8 | 48% | No |
| CVE-2026-45658 | Critical | 9.8 | 48% | No |
| CVE-2026-47289 | Critical | 9.8 | 48% | No |
| CVE-2026-47291 | Critical | 9.8 | 48% | No |
| CVE-2026-47648 | Critical | 9.8 | 48% | No |
| CVE-2026-47652 | Critical | 9.8 | 48% | No |
| CVE-2026-47653 | Critical | 9.8 | 48% | No |
| CVE-2026-47656 | Critical | 9.8 | 48% | No |
| CVE-2026-48563 | Critical | 9.8 | 48% | No |
| CVE-2026-48568 | Critical | 9.8 | 48% | No |
| CVE-2026-48570 | Critical | 9.8 | 48% | No |
| CVE-2026-48573 | Critical | 9.8 | 48% | No |
| CVE-2026-48574 | Critical | 9.8 | 48% | No |
| CVE-2026-48575 | Critical | 9.8 | 48% | No |
| CVE-2026-48576 | Critical | 9.8 | 48% | No |
| CVE-2026-48578 | Critical | 9.8 | 48% | No |
| CVE-2026-48583 | Critical | 9.8 | 48% | No |
| CVE-2026-49160 | Critical | 9.8 | 48% | No |
| CVE-2026-50507 | Critical | 9.8 | 48% | No |
| CVE-2026-50508 | Critical | 9.8 | 48% | No |
| CVE-2026-8863 | Critical | 9.8 | 48% | No |
What the press says about this update
Trusted-source coverage of the CVEs this update fixes, pulled live from their own feeds.
Affected products
Also released in June 2026
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5093998
Any of these paths delivers KB5093998; 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 KB5093998 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 KB5093998, ranked by exploitation.
Common questions about KB5093998
Does KB5093998 have known issues?
Yes. Microsoft's support article documents known issues for KB5093998 (checked 2026-07-21). The Known issues section on this page quotes it; verify against the article before acting.
Is KB5093998 urgent?
KB5093998 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 KB5093998?
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 KB5093998 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 KB5093998?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5093998'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.
