Patch tracker / KB5094127

KB5094127: Windows Server 2019 Security Update (June 2026)

KB5094127 is a Critical security update for Windows Server 2019, released 2026-06-09. It closes 148 CVEs with a maximum CVSS of 9.8. The most likely of them to be attacked is CVE-2026-33834, which FIRST.org rates at 80% probability of exploitation in the next 30 days.

Update summary

Critical
2026-06-09
Released
148
CVEs fixed
9.8
Max CVSS
Critical
Severity
Deploy this cycle
Fixes 148 CVEs for Windows Server 2019. No confirmed in-the-wild exploitation in this set today.

Fixes 148 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 54%. Among the top 25% of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

A newer security update for Windows 10 Version 1809 for 32-bit Systems has shipped since this one: KB5089548 (2026-07-14). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.

Senserva found thisread these before you deploy broadly

Microsoft documents 3 known issues with this update.

  • Microsoft Office applications might fail to open from certain third-party apps
  • Deleting from Recycle Bin displays an internal file name
  • OneDrive shortcut in File Explorer might not work in administrator mode

The full text, quoted from Microsoft

Senserva AI Opinion for KB5094127

KB5094127 is a large June 2026 rollup for Windows 10 1809 and Windows Server 2019 that closes 148 CVEs, topped by a Critical issue rated CVSS 9.8. One flaw carries a 54% EPSS score, meaning exploitation in the wild is more probable than not even though none of these CVEs are in CISA KEV or tied to ransomware yet. The combination of a large CVE count and a near-coin-flip exploit likelihood on the worst bug makes this a priority for any remaining 1809 and Server 2019 fleets.

Do this: Deploy KB5094127 to all Windows 10 1809 and Windows Server 2019 systems this cycle, prioritizing internet-facing Server 2019 hosts first.

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

Senserva AI Opinion and rich prompt for KB5094127

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for KB5094127

Released
2026-06-09
Last changed
2026-07-24
Changes tracked
2

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.

Check if KB5094127 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5094127 (checked 2026-08-05). 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.

Resolution

This issue is resolved in Windows updates released on and after July 14, 2026 such as KB5099539 . We recommend you install the latest Windows update for your device as it contains important improvements and ...

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.

CVESeverityCVSSEPSSExploited
CVE-2025-10263Critical9.854%No
CVE-2025-54518Critical9.880%No
CVE-2026-21530Critical9.880%No
CVE-2026-32161Critical9.880%No
CVE-2026-32170Critical9.880%No
CVE-2026-32209Critical9.880%No
CVE-2026-33828Critical9.854%No
CVE-2026-33834Critical9.880%No
CVE-2026-33835Critical9.880%No
CVE-2026-33837Critical9.880%No
CVE-2026-33838Critical9.880%No
CVE-2026-33839Critical9.880%No
CVE-2026-33841Critical9.880%No
CVE-2026-34329Critical9.880%No
CVE-2026-34330Critical9.880%No
CVE-2026-34331Critical9.880%No
CVE-2026-34333Critical9.880%No
CVE-2026-34334Critical9.880%No
CVE-2026-34335Critical9.854%No
CVE-2026-34336Critical9.880%No
CVE-2026-34337Critical9.880%No
CVE-2026-34338Critical9.880%No
CVE-2026-34339Critical9.880%No
CVE-2026-34340Critical9.880%No
CVE-2026-34341Critical9.880%No
CVE-2026-34342Critical9.880%No
CVE-2026-34343Critical9.880%No
CVE-2026-34344Critical9.880%No
CVE-2026-34345Critical9.880%No
CVE-2026-34347Critical9.880%No
CVE-2026-34351Critical9.880%No
CVE-2026-35415Critical9.880%No
CVE-2026-35416Critical9.880%No
CVE-2026-35417Critical9.880%No
CVE-2026-35418Critical9.880%No
CVE-2026-35421Critical9.880%No
CVE-2026-35422Critical9.880%No
CVE-2026-35423Critical9.880%No
CVE-2026-35424Critical9.880%No
CVE-2026-40377Critical9.880%No
CVE-2026-40380Critical9.880%No
CVE-2026-40382Critical9.880%No
CVE-2026-40397Critical9.880%No
CVE-2026-40398Critical9.880%No
CVE-2026-40399Critical9.880%No
CVE-2026-40401Critical9.880%No
CVE-2026-40403Critical9.880%No
CVE-2026-40404Critical9.854%No
CVE-2026-40406Critical9.880%No
CVE-2026-40407Critical9.880%No
CVE-2026-40408Critical9.880%No
CVE-2026-40409Critical9.854%No
CVE-2026-40410Critical9.880%No
CVE-2026-40413Critical9.880%No
CVE-2026-40414Critical9.880%No
CVE-2026-40415Critical9.880%No
CVE-2026-41088Critical9.880%No
CVE-2026-41092Critical9.854%No
CVE-2026-41097Critical9.880%No
CVE-2026-41108Critical9.854%No
CVE-2026-42825Critical9.880%No
CVE-2026-42828Critical9.854%No
CVE-2026-42836Critical9.854%No
CVE-2026-42837Critical9.854%No
CVE-2026-42903Critical9.854%No
CVE-2026-42904Critical9.854%No
CVE-2026-42905Critical9.854%No
CVE-2026-42906Critical9.854%No
CVE-2026-42907Critical9.854%No
CVE-2026-42908Critical9.854%No
CVE-2026-42909Critical9.854%No
CVE-2026-42911Critical9.854%No
CVE-2026-42912Critical9.854%No
CVE-2026-42914Critical9.854%No
CVE-2026-42915Critical9.854%No
CVE-2026-42916Critical9.854%No
CVE-2026-42968Critical9.854%No
CVE-2026-42969Critical9.854%No
CVE-2026-42970Critical9.854%No
CVE-2026-42971Critical9.854%No
CVE-2026-42972Critical9.854%No
CVE-2026-42973Critical9.854%No
CVE-2026-42977Critical9.854%No
CVE-2026-42978Critical9.854%No
CVE-2026-42979Critical9.854%No
CVE-2026-42980Critical9.854%No
CVE-2026-42983Critical9.854%No
CVE-2026-42984Critical9.854%No
CVE-2026-42985Critical9.854%No
CVE-2026-42986Critical9.854%No
CVE-2026-42989Critical9.854%No
CVE-2026-42991Critical9.854%No
CVE-2026-42992Critical9.854%No
CVE-2026-42993Critical9.854%No
CVE-2026-44799Critical9.854%No
CVE-2026-44801Critical9.854%No
CVE-2026-44802Critical9.854%No
CVE-2026-44803Critical9.854%No
CVE-2026-44812Critical9.854%No
CVE-2026-44815Critical9.854%No
CVE-2026-45487Critical9.854%No
CVE-2026-45586Critical9.854%No
CVE-2026-45588Critical9.854%No
CVE-2026-45592Critical9.854%No
CVE-2026-45593Critical9.854%No
CVE-2026-45594Critical9.854%No
CVE-2026-45595Critical9.854%No
CVE-2026-45596Critical9.854%No
CVE-2026-45598Critical9.854%No
CVE-2026-45599Critical9.854%No
CVE-2026-45601Critical9.854%No
CVE-2026-45602Critical9.854%No
CVE-2026-45603Critical9.854%No
CVE-2026-45605Critical9.854%No
CVE-2026-45606Critical9.854%No
CVE-2026-45607Critical9.854%No
CVE-2026-45608Critical9.854%No
CVE-2026-45634Critical9.854%No
CVE-2026-45635Critical9.854%No
CVE-2026-45636Critical9.854%No
CVE-2026-45637Critical9.854%No
CVE-2026-45638Critical9.854%No
CVE-2026-45639Critical9.854%No
CVE-2026-45640Critical9.854%No
CVE-2026-45641Critical9.854%No
CVE-2026-45642Critical9.854%No
CVE-2026-45653Critical9.854%No
CVE-2026-45655Critical9.854%No
CVE-2026-45656Critical9.854%No
CVE-2026-45658Critical9.854%No
CVE-2026-47289Critical9.854%No
CVE-2026-47291Critical9.854%No
CVE-2026-47648Critical9.854%No
CVE-2026-47653Critical9.854%No
CVE-2026-47656Critical9.854%No
CVE-2026-48563Critical9.854%No
CVE-2026-48568Critical9.854%No
CVE-2026-48570Critical9.854%No
CVE-2026-48573Critical9.854%No
CVE-2026-48574Critical9.854%No
CVE-2026-48575Critical9.854%No
CVE-2026-48576Critical9.854%No
CVE-2026-48578Critical9.854%No
CVE-2026-48583Critical9.854%No
CVE-2026-49160Critical9.854%No
CVE-2026-50507Critical9.854%No
CVE-2026-50508Critical9.854%No
CVE-2026-8863Critical9.854%No

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.