Patch tracker / KB5120238

KB5120238: Windows Server 2019 Security Update (August 2026)

KB5120238 is a Critical security update for Windows Server 2019, released 2026-08-11. It closes 183 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. The most likely of them to be attacked is CVE-2026-68820, which FIRST.org rates at 9% probability of exploitation in the next 30 days.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Update summary

CriticalCISA KEV
2026-08-11
Released
183
CVEs fixed
9.8
Max CVSS v3
Critical
Severity
Deploy now
This update fixes vulnerabilities confirmed exploited in the wild.

Fixes 183 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 8.6%. Among the top half 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 x64-based Systems has shipped since this one: KB5131085 (2026-11-10). 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 thisno known issues as of our last check

We checked Microsoft's support article for KB5120238 on 2026-11-09 and it lists no known issues. Read the article before broad deployment; Microsoft adds issues as reports come in, and we re-check on every refresh.

Senserva AI Opinion for KB5120238

KB5120238 is the August 2026 cumulative update for Windows 10 Version 1809 and Windows Server 2019 (including Server Core), and it fixes 174 CVEs in one pass, which is an unusually large batch for an older servicing branch. At least one of those CVEs is on the CISA Known Exploited Vulnerabilities list (not tied to ransomware), the top Severity is Critical at CVSS 9.8, and the highest EPSS is 9%, so exploitation is already confirmed in the wild rather than merely possible. Anyone still running 1809 or Server 2019, especially Server Core hosts that are easy to overlook, is exposed until this is applied.

Do this: Deploy KB5120238 to Windows Server 2019 and Windows 10 1809 systems today, starting with internet-facing and Server Core hosts, since the KEV-listed CVE is already being exploited.

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

Senserva AI Opinion and rich prompt for KB5120238

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

Full tracking and change history for KB5120238

Released
2026-08-11
Last changed
2026-11-11
Changes tracked
12

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.

Senserva Watchevery change we have recorded for this one
What changed, and when
  • 2026-08-12 CVEs fixed 181 to 182
  • 2026-08-20 CVEs fixed 182 to 183

Recorded by Senserva on the dates shown, from the MSRC release feed. This is what moved and when, which neither the vendor advisory nor NVD publishes.

Check if KB5120238 is installed

Elevated PowerShell. No output means it is not installed.

From the Senserva blog

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-2026-68820High7.08.6%KEV
CVE-2026-62878Critical9.8<1%No
CVE-2026-62893Critical9.8<1%No
CVE-2026-65791Critical9.8<1%No
CVE-2026-49179High8.8<1%No
CVE-2026-62784High8.8<1%No
CVE-2026-62785High8.8<1%No
CVE-2026-62790High8.8<1%No
CVE-2026-62795High8.8<1%No
CVE-2026-62800High8.8<1%No
CVE-2026-62816High8.8<1%No
CVE-2026-62817High8.8<1%No
CVE-2026-62818High8.8<1%No
CVE-2026-62822High8.8<1%No
CVE-2026-62823High8.8<1%No
CVE-2026-62778High8.1<1%No
CVE-2026-62781High8.1<1%No
CVE-2026-62792High8.1<1%No
CVE-2026-62819High8.1<1%No
CVE-2026-62820High8.1<1%No
CVE-2026-62889High8.1<1%No
CVE-2026-65679High8.1<1%No
CVE-2026-65789High8.1<1%No
CVE-2026-65796High8.1<1%No
CVE-2026-66802High8.1<1%No
CVE-2026-71331High8.1<1%No
CVE-2026-6726High7.9<1%No
CVE-2026-42976High7.8<1%No
CVE-2026-54984High7.8<1%No
CVE-2026-56174High7.8<1%No
CVE-2026-59127High7.8<1%No
CVE-2026-61349High7.8<1%No
CVE-2026-61353High7.8<1%No
CVE-2026-61356High7.8<1%No
CVE-2026-61358High7.8<1%No
CVE-2026-61364High7.8<1%No
CVE-2026-61365High7.8<1%No
CVE-2026-61367High7.8<1%No
CVE-2026-61923High7.8<1%No
CVE-2026-61925High7.8<1%No
CVE-2026-61926High7.8<1%No
CVE-2026-61930High7.8<1%No
CVE-2026-61932High7.8<1%No
CVE-2026-61937High7.8<1%No
CVE-2026-62692High7.8<1%No
CVE-2026-62696High7.8<1%No
CVE-2026-62698High7.8<1%No
CVE-2026-62700High7.8<1%No
CVE-2026-62701High7.8<1%No
CVE-2026-62707High7.8<1%No
CVE-2026-62710High7.8<1%No
CVE-2026-62711High7.8<1%No
CVE-2026-62712High7.8<1%No
CVE-2026-62713High7.8<1%No
CVE-2026-62717High7.8<1%No
CVE-2026-62719High7.8<1%No
CVE-2026-62721High7.8<1%No
CVE-2026-62732High7.8<1%No
CVE-2026-62733High7.8<1%No
CVE-2026-62735High7.8<1%No
CVE-2026-62739High7.8<1%No
CVE-2026-62741High7.8<1%No
CVE-2026-62747High7.8<1%No
CVE-2026-62752High7.8<1%No
CVE-2026-62754High7.8<1%No
CVE-2026-62755High7.8<1%No
CVE-2026-62758High7.8<1%No
CVE-2026-62761High7.8<1%No
CVE-2026-62768High7.8<1%No
CVE-2026-62770High7.8<1%No
CVE-2026-62771High7.8<1%No
CVE-2026-62776High7.8<1%No
CVE-2026-62777High7.8<1%No
CVE-2026-62783High7.8<1%No
CVE-2026-62797High7.8<1%No
CVE-2026-62803High7.8<1%No
CVE-2026-62807High7.8<1%No
CVE-2026-62812High7.8<1%No
CVE-2026-62876High7.8<1%No
CVE-2026-62877High7.8<1%No
CVE-2026-62880High7.8<1%No
CVE-2026-62885High7.8<1%No
CVE-2026-62890High7.8<1%No
CVE-2026-62894High7.8<1%No
CVE-2026-65671High7.8<1%No
CVE-2026-65773High7.8<1%No
CVE-2026-65774High7.8<1%No
CVE-2026-65775High7.8<1%No
CVE-2026-65786High7.8<1%No
CVE-2026-65787High7.8<1%No
CVE-2026-65790High7.8<1%No
CVE-2026-65814High7.8<1%No
CVE-2026-66799High7.8<1%No
CVE-2026-70344High7.8<1%No
CVE-2026-70345High7.8<1%No
CVE-2026-70346High7.8<1%No
CVE-2026-70347High7.8<1%No
CVE-2026-54113High7.51.2%No
CVE-2026-59132High7.51.2%No
CVE-2026-59134High7.5<1%No
CVE-2026-61352High7.5<1%No
CVE-2026-61363High7.5<1%No
CVE-2026-62787High7.5<1%No
CVE-2026-65681High7.51.2%No
CVE-2026-50472High7.0<1%No
CVE-2026-59122High7.0<1%No
CVE-2026-59125High7.0<1%No
CVE-2026-61346High7.0<1%No
CVE-2026-61348High7.0<1%No
CVE-2026-61366High7.0<1%No
CVE-2026-61939High7.0<1%No
CVE-2026-62690High7.0<1%No
CVE-2026-62723High7.0<1%No
CVE-2026-62724High7.0<1%No
CVE-2026-62725High7.0<1%No
CVE-2026-62726High7.0<1%No
CVE-2026-62727High7.0<1%No
CVE-2026-62728High7.0<1%No
CVE-2026-62729High7.0<1%No
CVE-2026-62734High7.0<1%No
CVE-2026-62748High7.0<1%No
CVE-2026-62753High7.0<1%No
CVE-2026-62773High7.0<1%No
CVE-2026-62774High7.0<1%No
CVE-2026-62892High7.0<1%No
CVE-2026-62908High7.0<1%No
CVE-2026-65678High7.0<1%No
CVE-2026-70307High7.0<1%No
CVE-2026-62699Medium6.8<1%No
CVE-2026-62769Medium6.7<1%No
CVE-2026-62881Medium6.7<1%No
CVE-2026-62883Medium6.7<1%No
CVE-2026-65795Medium6.7<1%No
CVE-2026-65797Medium6.7<1%No
CVE-2026-65798Medium6.7<1%No
CVE-2026-65799Medium6.7<1%No
CVE-2026-70304Medium6.7<1%No
CVE-2026-70330Medium6.7<1%No
CVE-2026-61920Medium6.6<1%No
CVE-2026-59138Medium6.51.1%No
CVE-2026-61345Medium6.51.1%No
CVE-2026-61918Medium6.5<1%No
CVE-2026-61921Medium6.5<1%No
CVE-2026-61924Medium6.5<1%No
CVE-2026-62714Medium6.5<1%No
CVE-2026-62715Medium6.5<1%No
CVE-2026-62716Medium6.5<1%No
CVE-2026-62718Medium6.5<1%No
CVE-2026-62720Medium6.5<1%No
CVE-2026-62742Medium6.5<1%No
CVE-2026-62745Medium6.5<1%No
CVE-2026-62750Medium6.5<1%No
CVE-2026-62782Medium6.5<1%No
CVE-2026-62814Medium6.5<1%No
CVE-2026-65794Medium6.5<1%No
CVE-2026-6727Medium5.9<1%No
CVE-2026-68819Medium5.9<1%No
CVE-2026-59130Medium5.6<1%No
CVE-2026-59131Medium5.6<1%No
CVE-2026-59128Medium5.5<1%No
CVE-2026-59135Medium5.5<1%No
CVE-2026-59136Medium5.5<1%No
CVE-2026-59137Medium5.5<1%No
CVE-2026-61347Medium5.5<1%No
CVE-2026-61360Medium5.5<1%No
CVE-2026-61928Medium5.5<1%No
CVE-2026-61936Medium5.5<1%No
CVE-2026-62703Medium5.5<1%No
CVE-2026-62709Medium5.5<1%No
CVE-2026-62730Medium5.5<1%No
CVE-2026-62738Medium5.5<1%No
CVE-2026-62740Medium5.5<1%No
CVE-2026-62743Medium5.5<1%No
CVE-2026-62746Medium5.5<1%No
CVE-2026-62786Medium5.5<1%No
CVE-2026-62793Medium5.5<1%No
CVE-2026-62796Medium5.5<1%No
CVE-2026-62887Medium5.5<1%No
CVE-2026-65662Medium5.5<1%No
CVE-2026-65784Medium5.5<1%No
CVE-2026-62757Medium5.3<1%No
CVE-2026-61368Medium5.0<1%No
CVE-2026-61350Medium4.6<1%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.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.