Patch tracker / KB5120385

KB5120385: Windows Server 2012 R2 Security Update (August 2026)

KB5120385 is a Critical security update for Windows Server 2012 R2, released 2026-08-11. It closes 144 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. It is the 12th largest of the 65 updates Microsoft shipped that month, by CVEs closed.

Update summary

CriticalCISA KEV

2026-08-11

Released

144

CVEs fixed

9.8

Max CVSS v3

Critical

Severity

Deploy now

This update fixes vulnerabilities confirmed exploited in the wild.

Fixes 144 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 1.2%. Among the lower 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 Server 2012 R2 has shipped since this one: KB5123066 (2026-09-08). 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 1 known issue with this update.

We are currently not aware of any issues with this update.

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5120385 Microsoft support article

Senserva AI Opinion and rich prompt for KB5120385

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

I am an IT admin triaging Microsoft updates. Facts for KB5120385 (source: https://senserva.com/kb/5120385.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- Update: KB5120385, Windows Server 2012 R2, released 2026-08-11
- Severity: Critical; fixes 144 CVEs, max CVSS 9.8
- Actively exploited (CISA KEV): YES
- CVEs include: CVE-2026-42976, CVE-2026-49179, CVE-2026-50472, CVE-2026-54984, CVE-2026-59122, CVE-2026-59127, CVE-2026-59128, CVE-2026-59130 and 136 more
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5120385
Using only these facts plus your general knowledge, tell me: 1) How urgent this update is and why, in two sentences. 2) Which systems should get it first. 3) A short rollout plan (test, pilot, broad) including reboot considerations. 4) What to verify after deployment.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for KB5120385

Released: 2026-08-11
Last changed: 2026-09-26
Changes tracked: 8

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

Microsoft revised KB5120385 on 2026-08-20: CVEs fixed 143 to 144.

2026-08-12 CVEs fixed 137 to 143
2026-08-20 CVEs fixed 143 to 144

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 KB5120385 is installed

Elevated PowerShell. No output means it is not installed.

# Is KB5120385 installed? (elevated PowerShell)
Get-HotFix -Id KB5120385 -ErrorAction SilentlyContinue

# Across many machines (replace the names):
Invoke-Command -ComputerName SERVER01,SERVER02 {
  Get-HotFix -Id KB5120385 -ErrorAction SilentlyContinue
} | Select-Object PSComputerName, HotFixID, InstalledOn

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5120385 (checked 2026-10-10). Verify against the article before acting.

We are currently not aware of any issues with this update.

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-68820	High	7.0	1.2%	KEV
CVE-2026-59128	Critical	9.8	1.2%	No
CVE-2026-59130	Critical	9.8	1.2%	No
CVE-2026-59131	Critical	9.8	1.2%	No
CVE-2026-59135	Critical	9.8	1.2%	No
CVE-2026-59136	Critical	9.8	1.2%	No
CVE-2026-59137	Critical	9.8	1.2%	No
CVE-2026-59138	Critical	9.8	1.2%	No
CVE-2026-61345	Critical	9.8	1.2%	No
CVE-2026-61347	Critical	9.8	1.2%	No
CVE-2026-61350	Critical	9.8	1.2%	No
CVE-2026-61360	Critical	9.8	1.2%	No
CVE-2026-61918	Critical	9.8	1.2%	No
CVE-2026-61920	Critical	9.8	1.2%	No
CVE-2026-61921	Critical	9.8	1.2%	No
CVE-2026-61924	Critical	9.8	1.2%	No
CVE-2026-62699	Critical	9.8	1.2%	No
CVE-2026-62709	Critical	9.8	1.2%	No
CVE-2026-62714	Critical	9.8	1.2%	No
CVE-2026-62715	Critical	9.8	1.2%	No
CVE-2026-62716	Critical	9.8	1.2%	No
CVE-2026-62718	Critical	9.8	1.2%	No
CVE-2026-62720	Critical	9.8	1.2%	No
CVE-2026-62730	Critical	9.8	1.2%	No
CVE-2026-62738	Critical	9.8	1.2%	No
CVE-2026-62740	Critical	9.8	1.2%	No
CVE-2026-62742	Critical	9.8	1.2%	No
CVE-2026-62743	Critical	9.8	1.2%	No
CVE-2026-62745	Critical	9.8	1.2%	No
CVE-2026-62746	Critical	9.8	1.2%	No
CVE-2026-62750	Critical	9.8	1.2%	No
CVE-2026-62757	Critical	9.8	1.2%	No
CVE-2026-62769	Critical	9.8	1.2%	No
CVE-2026-62786	Critical	9.8	1.2%	No
CVE-2026-62793	Critical	9.8	1.2%	No
CVE-2026-62796	Critical	9.8	1.2%	No
CVE-2026-62814	Critical	9.8	1.2%	No
CVE-2026-62878	Critical	9.8	1.2%	No
CVE-2026-62881	Critical	9.8	1.2%	No
CVE-2026-62883	Critical	9.8	1.2%	No
CVE-2026-62887	Critical	9.8	1.2%	No
CVE-2026-62893	Critical	9.8	1.2%	No
CVE-2026-65662	Critical	9.8	1.2%	No
CVE-2026-65784	Critical	9.8	1.2%	No
CVE-2026-65791	Critical	9.8	1.2%	No
CVE-2026-65794	Critical	9.8	1.2%	No
CVE-2026-65797	Critical	9.8	1.2%	No
CVE-2026-65798	Critical	9.8	1.2%	No
CVE-2026-65799	Critical	9.8	1.2%	No
CVE-2026-68819	Critical	9.8	1.2%	No
CVE-2026-70304	Critical	9.8	1.2%	No
CVE-2026-70330	Critical	9.8	1.2%	No
CVE-2026-49179	High	8.8	1.2%	No
CVE-2026-62784	High	8.8	1.2%	No
CVE-2026-62785	High	8.8	1.2%	No
CVE-2026-62790	High	8.8	1.2%	No
CVE-2026-62795	High	8.8	1.2%	No
CVE-2026-62800	High	8.8	1.2%	No
CVE-2026-62816	High	8.8	1.2%	No
CVE-2026-62818	High	8.8	1.2%	No
CVE-2026-62822	High	8.8	1.2%	No
CVE-2026-62823	High	8.8	1.2%	No
CVE-2026-62824	High	8.8	1.2%	No
CVE-2026-62778	High	8.1	1.2%	No
CVE-2026-62781	High	8.1	1.2%	No
CVE-2026-62792	High	8.1	1.2%	No
CVE-2026-62819	High	8.1	1.2%	No
CVE-2026-62889	High	8.1	1.2%	No
CVE-2026-65679	High	8.1	1.2%	No
CVE-2026-65796	High	8.1	1.2%	No
CVE-2026-42976	High	7.8	1.2%	No
CVE-2026-54984	High	7.8	1.2%	No
CVE-2026-59127	High	7.8	1.2%	No
CVE-2026-61349	High	7.8	1.2%	No
CVE-2026-61353	High	7.8	1.2%	No
CVE-2026-61364	High	7.8	1.2%	No
CVE-2026-61365	High	7.8	1.2%	No
CVE-2026-61367	High	7.8	1.2%	No
CVE-2026-61925	High	7.8	1.2%	No
CVE-2026-61926	High	7.8	1.2%	No
CVE-2026-61937	High	7.8	1.2%	No
CVE-2026-62692	High	7.8	1.2%	No
CVE-2026-62698	High	7.8	1.2%	No
CVE-2026-62700	High	7.8	1.2%	No
CVE-2026-62701	High	7.8	1.2%	No
CVE-2026-62711	High	7.8	1.2%	No
CVE-2026-62712	High	7.8	1.2%	No
CVE-2026-62717	High	7.8	1.2%	No
CVE-2026-62719	High	7.8	1.2%	No
CVE-2026-62721	High	7.8	1.2%	No
CVE-2026-62732	High	7.8	1.2%	No
CVE-2026-62733	High	7.8	1.2%	No
CVE-2026-62735	High	7.8	1.2%	No
CVE-2026-62741	High	7.8	1.2%	No
CVE-2026-62752	High	7.8	1.2%	No
CVE-2026-62754	High	7.8	1.2%	No
CVE-2026-62755	High	7.8	1.2%	No
CVE-2026-62758	High	7.8	1.2%	No
CVE-2026-62761	High	7.8	1.2%	No
CVE-2026-62768	High	7.8	1.2%	No
CVE-2026-62770	High	7.8	1.2%	No
CVE-2026-62776	High	7.8	1.2%	No
CVE-2026-62797	High	7.8	1.2%	No
CVE-2026-62803	High	7.8	1.2%	No
CVE-2026-62807	High	7.8	1.2%	No
CVE-2026-62812	High	7.8	1.2%	No
CVE-2026-62876	High	7.8	1.2%	No
CVE-2026-62877	High	7.8	1.2%	No
CVE-2026-62880	High	7.8	1.2%	No
CVE-2026-62885	High	7.8	1.2%	No
CVE-2026-62890	High	7.8	1.2%	No
CVE-2026-65671	High	7.8	1.2%	No
CVE-2026-65774	High	7.8	1.2%	No
CVE-2026-65775	High	7.8	1.2%	No
CVE-2026-65790	High	7.8	1.2%	No
CVE-2026-65814	High	7.8	1.2%	No
CVE-2026-66799	High	7.8	1.2%	No
CVE-2026-70344	High	7.8	1.2%	No
CVE-2026-70345	High	7.8	1.2%	No
CVE-2026-70346	High	7.8	1.2%	No
CVE-2026-70347	High	7.8	1.2%	No
CVE-2026-59132	High	7.5	1.2%	No
CVE-2026-59134	High	7.5	1.2%	No
CVE-2026-61352	High	7.5	1.2%	No
CVE-2026-61363	High	7.5	1.2%	No
CVE-2026-62787	High	7.5	1.2%	No
CVE-2026-50472	High	7.0	1.2%	No
CVE-2026-59122	High	7.0	1.2%	No
CVE-2026-61348	High	7.0	1.2%	No
CVE-2026-61366	High	7.0	1.2%	No
CVE-2026-61939	High	7.0	1.2%	No
CVE-2026-62723	High	7.0	1.2%	No
CVE-2026-62724	High	7.0	1.2%	No
CVE-2026-62725	High	7.0	1.2%	No
CVE-2026-62726	High	7.0	1.2%	No
CVE-2026-62727	High	7.0	1.2%	No
CVE-2026-62728	High	7.0	1.2%	No
CVE-2026-62729	High	7.0	1.2%	No
CVE-2026-62734	High	7.0	1.2%	No
CVE-2026-62748	High	7.0	1.2%	No
CVE-2026-62753	High	7.0	1.2%	No
CVE-2026-62773	High	7.0	1.2%	No
CVE-2026-62908	High	7.0	1.2%	No
CVE-2026-70307	High	7.0	1.2%	No

Scope and sources

Affected products

Also released in August 2026

Authoritative references

Official KB5120385 page (Microsoft Support)Microsoft Update Catalog Microsoft Security Update Guide

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

KB5120385: Windows Server 2012 R2 Security Update (August 2026)

Update summary

Full tracking and change history for KB5120385

Check if KB5120385 is installed

Known issues, from Microsoft

CVEs fixed by this update

Scope and sources

KB5120228

KB5120229

KB5120233

KB5120238

KB5120240

KB5120242

KB5120386

KB5120418