Patch tracker / KB5121003

KB5121003: Windows Server 2022 Security Update (August 2026)

KB5121003 is a Critical security update for Windows Server 2022, released 2026-08-11. It closes 194 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-42976, which FIRST.org rates at 54% probability of exploitation in the next 30 days.

Update summary

CriticalCISA KEV

2026-08-11

Released

194

CVEs fixed

9.8

Max CVSS v3

Critical

Severity

Deploy now

This update fixes vulnerabilities confirmed exploited in the wild.

Fixes 194 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 6.2%. 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: KB5122871 (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 2 known issues with this update.

Reports of certain games becoming unresponsive
Microsoft Teams and Outlook might fail to launch on ARM-based devices

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5121003 Microsoft support article

Senserva AI Opinion and rich prompt for KB5121003

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 KB5121003 (source: https://senserva.com/kb/5121003.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (morning and afternoon US Central)):
- Update: KB5121003, Windows Server 2022, released 2026-08-11
- Severity: Critical; fixes 194 CVEs, max CVSS 9.8
- Actively exploited (CISA KEV): YES
- CVEs include: CVE-2026-42976, CVE-2026-49179, CVE-2026-50472, CVE-2026-54113, CVE-2026-54984, CVE-2026-56179, CVE-2026-59122, CVE-2026-59125 and 186 more
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5121003
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 KB5121003

Released: 2026-08-11
Last changed: 2026-09-15
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

The strongest signal is the single recorded change on 2026-08-20, when the CVE fix count moved from 195 to 196. This is a single point with no earlier history to compare against, so the direction is a modest increase of one addressed CVE. For an IT admin today, treat this as a stable update with incremental coverage and plan deployment accordingly.

2026-08-20 CVEs fixed 195 to 196

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

Elevated PowerShell. No output means it is not installed.

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

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

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5121003 (checked 2026-09-18). Verify against the article before acting.

Reports of certain games becoming unresponsive

Symptoms

Microsoft received reports of issues involving inability to run certain games as expected after installing this update.

Ongoing investigation indicates that this issue is associated with certain peripherals or internal device components that support RGB lighting features. These devices might install drivers or software components with file names similar to inpoutx64 . On systems where these drivers are found, launching certain games can trigger this issue.

Games identified in reports of this issue include ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS. Reported symptoms include:

the game application becomes unresponsive

the game application closes without notice

the error "EXCEPTION_ACCESS_VIOLATION" is displayed

the device restarts without warning

If you are experiencing this issue or a similar issue, please use Feedback Hub to submit a report. You can open Feedback Hub by pressing the Windows logo key + F . For additional information, see Send feedback to Microsoft with the Feedback Hub app . Your reports are helpful to our investigation.

Resolution

This issue is resolved by a block that prevents the inpoutx64 driver from loading on affected devices. When the block is applied, a message is displayed that states the driver has been disabled, after which the game will launch normally.

This resolution is available automatically to consumer and business devices that are not managed by IT departments. For enterprise-managed devices, the mitigation will not propagate automatically. IT administrators can follow the steps in the workaround section on the Windows release health site .

Microsoft Teams and Outlook might fail to launch on ARM-based devices

Symptoms

After installing Windows security updates released on or after August 11, 2026, (KB5121003) , Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates.

Workaround

To work around this issue:

Open Microsoft Store.

Select Downloads > Check for updates.

Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later).

Resolution

This issue is resolved in Windows updates released on and after September 8, 2026 such as KB5124008 . We recommend you install the latest Windows update for your device as it contains ...

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	6.2%	KEV
CVE-2026-59128	Critical	9.8	6.2%	No
CVE-2026-59130	Critical	9.8	6.2%	No
CVE-2026-59131	Critical	9.8	6.2%	No
CVE-2026-59135	Critical	9.8	6.2%	No
CVE-2026-59136	Critical	9.8	6.2%	No
CVE-2026-59137	Critical	9.8	6.2%	No
CVE-2026-61347	Critical	9.8	6.2%	No
CVE-2026-61350	Critical	9.8	6.2%	No
CVE-2026-61360	Critical	9.8	6.2%	No
CVE-2026-61368	Critical	9.8	6.2%	No
CVE-2026-61928	Critical	9.8	6.2%	No
CVE-2026-61933	Critical	9.8	6.2%	No
CVE-2026-61936	Critical	9.8	6.2%	No
CVE-2026-62703	Critical	9.8	6.2%	No
CVE-2026-62709	Critical	9.8	6.2%	No
CVE-2026-62730	Critical	9.8	6.2%	No
CVE-2026-62738	Critical	9.8	6.2%	No
CVE-2026-62740	Critical	9.8	6.2%	No
CVE-2026-62743	Critical	9.8	6.2%	No
CVE-2026-62746	Critical	9.8	6.2%	No
CVE-2026-62757	Critical	9.8	6.2%	No
CVE-2026-62786	Critical	9.8	6.2%	No
CVE-2026-62793	Critical	9.8	6.2%	No
CVE-2026-62796	Critical	9.8	6.2%	No
CVE-2026-62798	Critical	9.8	6.2%	No
CVE-2026-62815	Critical	9.8	6.2%	No
CVE-2026-62887	Critical	9.8	6.2%	No
CVE-2026-65662	Critical	9.8	6.2%	No
CVE-2026-65777	Critical	9.8	6.2%	No
CVE-2026-65784	Critical	9.8	6.2%	No
CVE-2026-6727	Critical	9.8	6.2%	No
CVE-2026-70348	Critical	9.8	6.2%	No
CVE-2026-49179	High	8.8	6.2%	No
CVE-2026-62784	High	8.8	6.2%	No
CVE-2026-62785	High	8.8	6.2%	No
CVE-2026-62790	High	8.8	6.2%	No
CVE-2026-62795	High	8.8	6.2%	No
CVE-2026-62800	High	8.8	6.2%	No
CVE-2026-62816	High	8.8	6.2%	No
CVE-2026-62822	High	8.8	6.2%	No
CVE-2026-56179	High	8.3	6.2%	No
CVE-2026-62781	High	8.1	6.2%	No
CVE-2026-62792	High	8.1	6.2%	No
CVE-2026-62819	High	8.1	6.2%	No
CVE-2026-62889	High	8.1	6.2%	No
CVE-2026-6726	High	7.9	6.2%	No
CVE-2026-42976	High	7.8	54%	No
CVE-2026-54984	High	7.8	6.2%	No
CVE-2026-59127	High	7.8	6.2%	No
CVE-2026-61349	High	7.8	6.2%	No
CVE-2026-61353	High	7.8	6.2%	No
CVE-2026-61355	High	7.8	6.2%	No
CVE-2026-61356	High	7.8	6.2%	No
CVE-2026-61357	High	7.8	6.2%	No
CVE-2026-61358	High	7.8	6.2%	No
CVE-2026-61359	High	7.8	6.2%	No
CVE-2026-61364	High	7.8	6.2%	No
CVE-2026-61365	High	7.8	6.2%	No
CVE-2026-61367	High	7.8	6.2%	No
CVE-2026-61923	High	7.8	6.2%	No
CVE-2026-61925	High	7.8	6.2%	No
CVE-2026-61926	High	7.8	6.2%	No
CVE-2026-61930	High	7.8	6.2%	No
CVE-2026-61934	High	7.8	6.2%	No
CVE-2026-61937	High	7.8	6.2%	No
CVE-2026-62688	High	7.8	6.2%	No
CVE-2026-62692	High	7.8	6.2%	No
CVE-2026-62695	High	7.8	6.2%	No
CVE-2026-62696	High	7.8	6.2%	No
CVE-2026-62698	High	7.8	6.2%	No
CVE-2026-62700	High	7.8	6.2%	No
CVE-2026-62701	High	7.8	6.2%	No
CVE-2026-62707	High	7.8	6.2%	No
CVE-2026-62710	High	7.8	6.2%	No
CVE-2026-62711	High	7.8	6.2%	No
CVE-2026-62712	High	7.8	6.2%	No
CVE-2026-62713	High	7.8	6.2%	No
CVE-2026-62717	High	7.8	6.2%	No
CVE-2026-62719	High	7.8	6.2%	No
CVE-2026-62722	High	7.8	6.2%	No
CVE-2026-62732	High	7.8	6.2%	No
CVE-2026-62733	High	7.8	6.2%	No
CVE-2026-62735	High	7.8	6.2%	No
CVE-2026-62736	High	7.8	6.2%	No
CVE-2026-62737	High	7.8	6.2%	No
CVE-2026-62739	High	7.8	6.2%	No
CVE-2026-62741	High	7.8	6.2%	No
CVE-2026-62747	High	7.8	6.2%	No
CVE-2026-62751	High	7.8	6.2%	No
CVE-2026-62752	High	7.8	6.2%	No
CVE-2026-62754	High	7.8	6.2%	No
CVE-2026-62755	High	7.8	6.2%	No
CVE-2026-62758	High	7.8	6.2%	No
CVE-2026-62768	High	7.8	6.2%	No
CVE-2026-62770	High	7.8	6.2%	No
CVE-2026-62771	High	7.8	6.2%	No
CVE-2026-62777	High	7.8	6.2%	No
CVE-2026-62779	High	7.8	6.2%	No
CVE-2026-62783	High	7.8	6.2%	No
CVE-2026-62797	High	7.8	6.2%	No
CVE-2026-62811	High	7.8	6.2%	No
CVE-2026-62832	High	7.8	6.2%	No
CVE-2026-62876	High	7.8	6.2%	No
CVE-2026-62877	High	7.8	6.2%	No
CVE-2026-62880	High	7.8	6.2%	No
CVE-2026-62885	High	7.8	6.2%	No
CVE-2026-62888	High	7.8	6.2%	No
CVE-2026-62890	High	7.8	6.2%	No
CVE-2026-62894	High	7.8	6.2%	No
CVE-2026-65671	High	7.8	6.2%	No
CVE-2026-65672	High	7.8	6.2%	No
CVE-2026-65773	High	7.8	6.2%	No
CVE-2026-65774	High	7.8	6.2%	No
CVE-2026-65775	High	7.8	6.2%	No
CVE-2026-65786	High	7.8	6.2%	No
CVE-2026-65787	High	7.8	6.2%	No
CVE-2026-65790	High	7.8	6.2%	No
CVE-2026-65814	High	7.8	6.2%	No
CVE-2026-66799	High	7.8	6.2%	No
CVE-2026-66804	High	7.8	6.2%	No
CVE-2026-70344	High	7.8	6.2%	No
CVE-2026-70345	High	7.8	6.2%	No
CVE-2026-70346	High	7.8	6.2%	No
CVE-2026-70347	High	7.8	6.2%	No
CVE-2026-54113	High	7.5	6.2%	No
CVE-2026-59132	High	7.5	6.2%	No
CVE-2026-59134	High	7.5	6.2%	No
CVE-2026-61352	High	7.5	6.2%	No
CVE-2026-61363	High	7.5	6.2%	No
CVE-2026-50472	High	7.0	6.2%	No
CVE-2026-59122	High	7.0	6.2%	No
CVE-2026-59125	High	7.0	6.2%	No
CVE-2026-59126	High	7.0	6.2%	No
CVE-2026-61346	High	7.0	6.2%	No
CVE-2026-61348	High	7.0	6.2%	No
CVE-2026-61361	High	7.0	6.2%	No
CVE-2026-61366	High	7.0	6.2%	No
CVE-2026-61927	High	7.0	6.2%	No
CVE-2026-61929	High	7.0	6.2%	No
CVE-2026-61938	High	7.0	6.2%	No
CVE-2026-61939	High	7.0	6.2%	No
CVE-2026-62690	High	7.0	6.2%	No
CVE-2026-62693	High	7.0	6.2%	No
CVE-2026-62705	High	7.0	6.2%	No
CVE-2026-62723	High	7.0	6.2%	No
CVE-2026-62724	High	7.0	6.2%	No
CVE-2026-62725	High	7.0	6.2%	No
CVE-2026-62726	High	7.0	6.2%	No
CVE-2026-62727	High	7.0	6.2%	No
CVE-2026-62728	High	7.0	6.2%	No
CVE-2026-62729	High	7.0	6.2%	No
CVE-2026-62734	High	7.0	6.2%	No
CVE-2026-62748	High	7.0	6.2%	No
CVE-2026-62749	High	7.0	6.2%	No
CVE-2026-62753	High	7.0	6.2%	No
CVE-2026-62766	High	7.0	6.2%	No
CVE-2026-62773	High	7.0	6.2%	No
CVE-2026-62774	High	7.0	6.2%	No
CVE-2026-62780	High	7.0	6.2%	No
CVE-2026-62788	High	7.0	6.2%	No
CVE-2026-62892	High	7.0	6.2%	No
CVE-2026-62908	High	7.0	6.2%	No
CVE-2026-65678	High	7.0	6.2%	No
CVE-2026-65776	High	7.0	6.2%	No
CVE-2026-65778	High	7.0	6.2%	No
CVE-2026-65779	High	7.0	6.2%	No
CVE-2026-65780	High	7.0	6.2%	No
CVE-2026-65781	High	7.0	6.2%	No
CVE-2026-65782	High	7.0	6.2%	No
CVE-2026-65783	High	7.0	6.2%	No
CVE-2026-65788	High	7.0	6.2%	No
CVE-2026-70307	High	7.0	6.2%	No
CVE-2026-62699	Medium	6.8	6.2%	No
CVE-2026-62702	Medium	6.8	6.2%	No
CVE-2026-62769	Medium	6.7	6.2%	No
CVE-2026-62881	Medium	6.7	6.2%	No
CVE-2026-62883	Medium	6.7	6.2%	No
CVE-2026-65795	Medium	6.7	6.2%	No
CVE-2026-65797	Medium	6.7	6.2%	No
CVE-2026-65798	Medium	6.7	6.2%	No
CVE-2026-65799	Medium	6.7	6.2%	No
CVE-2026-70304	Medium	6.7	6.2%	No
CVE-2026-70330	Medium	6.7	6.2%	No
CVE-2026-59138	Medium	6.5	6.2%	No
CVE-2026-61345	Medium	6.5	6.2%	No
CVE-2026-61918	Medium	6.5	6.2%	No
CVE-2026-61921	Medium	6.5	6.2%	No
CVE-2026-61924	Medium	6.5	6.2%	No
CVE-2026-62750	Medium	6.5	6.2%	No
CVE-2026-62782	Medium	6.5	6.2%	No
CVE-2026-65785	Medium	6.5	6.2%	No
CVE-2026-65794	Medium	6.5	6.2%	No
CVE-2026-62708	Medium	6.4	6.2%	No

Scope and sources

Affected products

Also released in August 2026

Authoritative references

Official KB5121003 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.

KB5121003: Windows Server 2022 Security Update (August 2026)

Update summary

Full tracking and change history for KB5121003

Check if KB5121003 is installed

Known issues, from Microsoft

CVEs fixed by this update

Scope and sources

KB5002882

KB5002883

KB5002891

KB5120228

KB5120229

KB5120233

KB5120238

KB5120240