Patch tracker / KB5121003

KB5121003: Windows 11 Version 25H2 Security Update (August 2026)

KB5121003 is a Critical security update for Windows 11 Version 25H2, released 2026-08-11. It closes 182 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so it is urgent, and Microsoft lists 2 known issues: test it before broad deployment. 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
182
CVEs fixed
9.8
Max CVSS v3
Critical
Severity
Test, then deploy
This update fixes vulnerabilities confirmed exploited in the wild. Microsoft lists 2 known issues.

Fixes 182 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 11 Version 25H2 for x64-based Systems has shipped since this one: KB5127648 (2026-10-13). 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

Senserva AI Opinion and rich prompt for KB5121003

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

Full tracking and change history for KB5121003

Released
2026-08-11
Last changed
2026-10-30
Changes tracked
14

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

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5121003 (checked 2026-10-29). Microsoft lists 2 known issues. Verify against the article before acting.

1. 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 .

2. 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 important improvements and issue resolutions, including this one.

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-62815Critical9.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-62816High8.8<1%No
CVE-2026-62822High8.8<1%No
CVE-2026-56179High8.3<1%No
CVE-2026-62781High8.1<1%No
CVE-2026-62792High8.1<1%No
CVE-2026-62819High8.1<1%No
CVE-2026-62889High8.1<1%No
CVE-2026-6726High7.9<1%No
CVE-2026-42976High7.8<1%No
CVE-2026-54984High7.8<1%No
CVE-2026-61349High7.8<1%No
CVE-2026-61353High7.8<1%No
CVE-2026-61355High7.8<1%No
CVE-2026-61356High7.8<1%No
CVE-2026-61357High7.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-61934High7.8<1%No
CVE-2026-61937High7.8<1%No
CVE-2026-62692High7.8<1%No
CVE-2026-62695High7.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-62722High7.8<1%No
CVE-2026-62732High7.8<1%No
CVE-2026-62733High7.8<1%No
CVE-2026-62735High7.8<1%No
CVE-2026-62736High7.8<1%No
CVE-2026-62737High7.8<1%No
CVE-2026-62739High7.8<1%No
CVE-2026-62741High7.8<1%No
CVE-2026-62747High7.8<1%No
CVE-2026-62751High7.8<1%No
CVE-2026-62754High7.8<1%No
CVE-2026-62755High7.8<1%No
CVE-2026-62758High7.8<1%No
CVE-2026-62768High7.8<1%No
CVE-2026-62770High7.8<1%No
CVE-2026-62771High7.8<1%No
CVE-2026-62777High7.8<1%No
CVE-2026-62779High7.8<1%No
CVE-2026-62783High7.8<1%No
CVE-2026-62797High7.8<1%No
CVE-2026-62811High7.8<1%No
CVE-2026-62876High7.8<1%No
CVE-2026-62880High7.8<1%No
CVE-2026-62885High7.8<1%No
CVE-2026-62888High7.8<1%No
CVE-2026-62890High7.8<1%No
CVE-2026-62894High7.8<1%No
CVE-2026-65671High7.8<1%No
CVE-2026-65672High7.8<1%No
CVE-2026-65773High7.8<1%No
CVE-2026-65774High7.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-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-50472High7.0<1%No
CVE-2026-59122High7.0<1%No
CVE-2026-59125High7.0<1%No
CVE-2026-59126High7.0<1%No
CVE-2026-61348High7.0<1%No
CVE-2026-61361High7.0<1%No
CVE-2026-61366High7.0<1%No
CVE-2026-61927High7.0<1%No
CVE-2026-61929High7.0<1%No
CVE-2026-61938High7.0<1%No
CVE-2026-61939High7.0<1%No
CVE-2026-62690High7.0<1%No
CVE-2026-62693High7.0<1%No
CVE-2026-62705High7.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-62749High7.0<1%No
CVE-2026-62753High7.0<1%No
CVE-2026-62766High7.0<1%No
CVE-2026-62773High7.0<1%No
CVE-2026-62774High7.0<1%No
CVE-2026-62780High7.0<1%No
CVE-2026-62788High7.0<1%No
CVE-2026-62892High7.0<1%No
CVE-2026-62908High7.0<1%No
CVE-2026-65678High7.0<1%No
CVE-2026-65776High7.0<1%No
CVE-2026-65778High7.0<1%No
CVE-2026-65779High7.0<1%No
CVE-2026-65780High7.0<1%No
CVE-2026-65781High7.0<1%No
CVE-2026-65782High7.0<1%No
CVE-2026-65783High7.0<1%No
CVE-2026-65788High7.0<1%No
CVE-2026-70307High7.0<1%No
CVE-2026-62699Medium6.8<1%No
CVE-2026-62702Medium6.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-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-62750Medium6.5<1%No
CVE-2026-62782Medium6.5<1%No
CVE-2026-65785Medium6.5<1%No
CVE-2026-65794Medium6.5<1%No
CVE-2026-62708Medium6.4<1%No
CVE-2026-6727Medium5.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-61933Medium5.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-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-62798Medium5.5<1%No
CVE-2026-62887Medium5.5<1%No
CVE-2026-65662Medium5.5<1%No
CVE-2026-65784Medium5.5<1%No
CVE-2026-70348Medium5.5<1%No
CVE-2026-62757Medium5.3<1%No
CVE-2026-65777Medium5.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.