Should you update to KB5131096?

From Windows updates, in the HARD wiki · Updated

Yes, today. KB5131096 is a security update Microsoft released on 10 Nov 2026 for Windows PCs. It fixes 547 security flaws, 31 rated critical and 516 important by Microsoft.[1] One of them is already being used in attacks.

Hear about the next Windows update the day it ships: get the alert below, or add the free HARD extension.

Should you update?

Yes, today. One of the flaws it fixes is already being used in attacks. It is the newest Windows 10 22H2 release. The holes it closes became public the moment it shipped, so waiting a week to see if others hit problems is the wrong trade.

Is KB5131096 safe to install?

Yes. It’s Microsoft’s own security release, and updates rarely go wrong; a backup makes it painless if one does. The one unsafe way to get it is from a link: Microsoft never sends updates by email, text or pop-up, so install it only from Start → Settings → Windows Update.

What it fixes

Microsoft lists 547 security flaws, 31 rated critical and 516 important by Microsoft.[1]

The critical and important fixes547
FlawSeverityWhat Microsoft calls it
CVE-2026-109459CriticalWindows Message Queuing Queue Manager Remote Code Execution Vulnerability
CVE-2026-111497CriticalGoogle: CVE-2026-111497 Buffer overflow vulnerability in the Brotli decoder
CVE-2026-112967CriticalWindows Xbox Live Networking Service Remote Code Execution Vulnerability
CVE-2026-113749CriticalMicrosoft Windows Codecs Library Remote Code Execution Vulnerability
CVE-2026-113752CriticalWindows Print Spooler Components Remote Code Execution Vulnerability
CVE-2026-113825CriticalWindows SMB Server Network Transport Driver (srvnet.sys) Remote Code Execution Vulnerability
CVE-2026-113856CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-113860CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-113861CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-113862CriticalWindows Network Address Translation (NAT) Remote Code Execution Vulnerability
CVE-2026-113864CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-113865CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-116710CriticalWindows Message Queuing Remote Code Execution Vulnerability
CVE-2026-116928CriticalWindows Search Remote Code Execution Vulnerability
CVE-2026-118145CriticalWindows Function Discovery SSDP Provider Remote Code Execution Vulnerability
CVE-2026-118146CriticalWindows Active Directory Domain Services Remote Code Execution Vulnerability
CVE-2026-118148CriticalActive Directory Domain Services Elevation of Privilege Vulnerability
CVE-2026-118737CriticalRemote Procedure Call Runtime Remote Code Execution Vulnerability
CVE-2026-119382CriticalWindows TPM Elevation of Privilege Vulnerability
CVE-2026-119947CriticalWindows Hyper-V Elevation of Privilege Vulnerability
CVE-2026-119952CriticalWindows Schannel Remote Code Execution Vulnerability
CVE-2026-119958CriticalWindows LDAP - Lightweight Directory Access Protocol Remote Code Execution Vulnerability
CVE-2026-119961CriticalWindows Internet Information Services Remote Code Execution Vulnerability
CVE-2026-119962CriticalWindows CredSSP Remote Code Execution Vulnerability
CVE-2026-119963CriticalWindows Message Queuing Remote Code Execution Vulnerability
CVE-2026-119964CriticalWindows Message Queuing Remote Code Execution Vulnerability
CVE-2026-119967CriticalWindows Message Queuing Queue Manager Remote Code Execution Vulnerability
CVE-2026-119969CriticalGraphic Fonts Remote Code Execution Vulnerability
CVE-2026-125134CriticalWindows Function Discovery Resource Publication Remote Code Execution Vulnerability
CVE-2026-125136CriticalWindows Network Connected Devices Auto-Setup Service Remote Code Execution Vulnerability
and 517 more

Used in attacks. This fix closes a flaw attackers were already using before the update came out, on CISA’s list or in Microsoft’s own words:[2] CVE-2026-111497.

How to update, and how long it takes

Usually 15 to 60 minutes in all, with one or two restarts. You can keep working while it downloads.

  1. Save your work first.Windows restarts to finish the update, once or twice.
  2. Open Start → Settings → Windows Update.Select Check for updates. Windows downloads the month’s cumulative update; it includes every earlier fix.
  3. Restart when it asks.Select Restart now, or schedule it for tonight. Until it restarts, the fixes aren’t in place.
  4. Leave automatic updates on.In the same place, under Advanced options, turn on “Get me up to date” so restarts don’t wait for days.

To check it worked: Press Windows key + R, type winver and press Enter: it shows the OS build. It should say 19045.7846 or later.

For devices that stay on an older version, Microsoft released KB5132059 (598 security flaws), KB5132061 (595 security flaws), KB5135385 (3 security flaws), KB5132043 (596 security flaws) and KB5131087 (575 security flaws) the same day. Each fixes the same holes where they apply.

KB5126657 vs KB5131096

KB5126657, released 13 Oct 2026, fixed 954 security flaws, one already used in attacks. KB5131096 fixes 547 security flaws and includes the fixes before it, so going straight to KB5131096 gets you both; you never need KB5126657 first. It is the newest release so far.

Also released 10 Nov 2026: Microsoft 365 Apps 2610 build 20527.20196, Firefox 160, Thunderbird 160, Microsoft Edge 156.0.4314.80, Firefox ESR 153.7, Thunderbird ESR 153.7. Every release and the latest version: Windows updates; everything HARD tracks: Updates.

KB5126657 and KB5131096 side by side
ReleaseKB5126657KB5131096
Released
Security fixes954547
Critical, important22, 93231, 516
Used in attacks11

Questions and references

Questions10

When was KB5131096 released?

Microsoft released KB5131096 on 10 Nov 2026. It is the newest Windows 10 22H2 release so far.

What’s new in KB5131096?

Microsoft released it as a security update that fixes 547 security flaws, 31 rated critical and 516 important by Microsoft. One of them is already being used in attacks. This page covers those fixes; Microsoft’s own release notes have its full wording.

Should I update to KB5131096?

Yes, today. One of the flaws it fixes is already being used in attacks.

Is KB5131096 safe to install?

Yes. It’s Microsoft’s own security release, and updates rarely go wrong; a backup makes it painless if one does. The one unsafe way to get it is from a link: Microsoft never sends updates by email, text or pop-up, so install it only from Start → Settings → Windows Update.

How long does the KB5131096 update take?

Usually 15 to 60 minutes in all, with one or two restarts. You can keep working while it downloads.

Is KB5131096 the latest Windows 10 22H2 release?

Yes. It is the latest security release for Windows 10 22H2 that we track.

Which flaws fixed in KB5131096 were used in attacks?

One: CVE-2026-111497. They were either on CISA’s list of flaws being used in attacks or described that way by Microsoft.

Can I skip KB5131096?

You can, but you would stay open to 547 security flaws, 1 of them already used in attacks. KB5131096 includes the fixes from every earlier release, including KB5126657, so you never need to install them one by one.

What is the difference between KB5126657 and KB5131096?

KB5126657, released 13 Oct 2026, fixed 954 security flaws, one already used in attacks. KB5131096, released 10 Nov 2026, fixes 547 security flaws and includes the earlier fixes, so installing KB5131096 straight away covers both.

How do I check my installed Windows version?

Press Windows key + R, type winver and press Enter: it shows the OS build. It should say 19045.7846 or later.

References2
  1. ^ Microsoft. “KB5131096”, 10 Nov 2026.
  2. ^ Cybersecurity and Infrastructure Security Agency. “Known Exploited Vulnerabilities Catalog”.