Patch tracker / KB5094125
KB5094125: Windows Server 2019 Security Update (June 2026)
Updated July 21, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Microsoft security update released 2026-06-09. Fixes 109 CVEs.
All about KB5094125: the download, the Senserva AI read, what the press says about it, a PowerShell installed-check, install guidance, the CVEs it fixes, and its change history.
KB5094125 is a Critical security update for Windows Server 2019, released 2026-06-09. It closes 109 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 KB5094125
Get the official update for KB5094125. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5094125
KB5094125 is a large June 2026 rollup for Windows 10 1809 and Windows Server 2019 that closes 109 CVEs, topped by a Critical issue rated CVSS 9.8 with an EPSS of 48 percent, meaning nearly even odds of exploitation activity in the near term. No CVE here is in the CISA KEV catalog or tied to known ransomware yet, but the combination of a 9.8 score and elevated EPSS on legacy 1809 systems raises the stakes for anyone still running that branch. Server 2019 domain infrastructure and long-lived 1809 endpoints are the primary exposure.
Do this: Deploy KB5094125 to all Windows 10 1809 and Server 2019 hosts this cycle, prioritizing internet-facing and domain controller systems for the CVSS 9.8 fix.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5094125
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5094125
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 109 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 KB5094125 is missing on your devices.
Check if KB5094125 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.
Writing about KB5094125? 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-33828 | Critical | 9.8 | 48% | No |
| CVE-2026-34335 | Critical | 9.8 | 48% | No |
| CVE-2026-40404 | Critical | 9.8 | 48% | No |
| CVE-2026-40409 | Critical | 9.8 | 48% | No |
| CVE-2026-41092 | Critical | 9.8 | 48% | No |
| CVE-2026-41108 | Critical | 9.8 | 48% | 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-42910 | 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-42987 | 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-44805 | Critical | 9.8 | 48% | No |
| CVE-2026-44809 | 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-45585 | 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-45600 | 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-45648 | Critical | 9.8 | 48% | No |
| CVE-2026-45653 | Critical | 9.8 | 48% | No |
| CVE-2026-45654 | 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-47288 | 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-47654 | 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-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 KB5094125
Any of these paths delivers KB5094125; 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 KB5094125 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 KB5094125, ranked by exploitation.
Common questions about KB5094125
Is KB5094125 urgent?
KB5094125 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 KB5094125?
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 KB5094125 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 KB5094125?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5094125'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.
