While the words "unauthenticated remote code execution" naturally trigger alarm bells across enterprise operations centers, the technical telemetry inside the Microsoft Security Response Center (MSRC) advisory paints a nuanced risk profile. Understanding both the severity of a successful hit and the mechanical difficulty of pulling it off is essential for planning maintenance windows across web-facing infrastructure and developer workstations alike.
Official Vulnerability Telemetry and Status Summary
According to the official MSRC Update Guide data for CVE-2026-119961, Microsoft classifies the Windows Internet Information Services Remote Code Execution Vulnerability as Critical severity. Below is the complete, authoritative breakdown of the official metrics, weakness identifiers, and operational status flags:
- CVE Identifier: CVE-2026-119961
- Title: Windows Internet Information Services Remote Code Execution Vulnerability
- Severity: Critical
- CVSS Base Score: 8.1
- CVSS Temporal Score: 7.1
- CVSS Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness Classifications (CWE): CWE-362, CWE-416
- Exploitation Assessment: Exploitation Less Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
The official MSRC vulnerability description states:
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Internet Information Services allows an unauthorized attacker to execute code over a network.
Section Summary: CVE-2026-119961 carries a Critical severity rating with an 8.1 CVSS base score and a 7.1 temporal score, has not been publicly disclosed or exploited, is assessed as Exploitation Less Likely, and requires customer patching action.
Anatomy of the Flaw: Packets, Race Conditions, and Memory Safety
How does an attacker actually attempt to trigger this bug, and why does a Critical remote code execution (RCE) vulnerability stop at a CVSS base score of 8.1 rather than 9.8? Microsoft's official advisory facts answer both questions directly.
First, on the mechanics of delivery, MSRC notes that an unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network, and successful exploitation could allow the attacker to execute code on the target system with no authentication or user interaction required. That accounts for the AV:N/PR:N/UI:N (Attack Vector: Network, Privileges Required: None, User Interaction: None) and C:H/I:H/A:H (High impact to Confidentiality, Integrity, and Availability) portions of the CVSS vector.
Second, Microsoft explicitly clarifies the high attack complexity metric (AC:H): successful exploitation of this vulnerability requires an attacker to win a race condition.
From general industry knowledge of secure systems engineering and the MITRE Common Weakness Enumeration framework, the pairing of CWE-362 and CWE-416 tells a familiar story about multi-threaded server software:
- CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization / Race Condition): Web servers like IIS are built for concurrency, handling multiple simultaneous network packets and worker threads at high speed. When two threads access or modify a shared state without strict locking or atomic synchronization, timing collisions occur.
- CWE-416 (Use After Free): In native code, losing a synchronization race frequently causes one thread to free a block of memory while another thread still holds a pointer to it and attempts to use it. If an attacker can flood or time crafted network packets accurately enough to win that microscopic timing window and control the reallocated memory contents, a crash turns into arbitrary code execution.
Winning a network-borne race condition against a remote target is notoriously noisy and sensitive to network jitter, CPU load, and thread scheduling—which aligns logically with Microsoft's AC:H rating and Exploitation Less Likely assessment, as well as the E:U/RL:O/RC:C temporal vector components indicating unproven exploit maturity alongside an official fix and confirmed report confidence. Still, anyone who has watched security research evolve knows that timing hurdles are speed bumps, not brick walls, especially on low-latency local networks or heavily loaded web servers.
Section Summary: Attackers target CVE-2026-119961 by sending specially crafted packets over the network without needing credentials or user interaction, but they must win a CWE-362 race condition linked to CWE-416 memory handling to achieve code execution.
Why Desktop Windows Editions Are on the Patch List
A fair rhetorical question often pops up on WindowsForum.com patch threads whenever an IIS advisory drops: Why am I patching a web server vulnerability on Windows 10 and Windows 11 desktops?
Based on standard Windows architecture knowledge, Internet Information Services is shipped as a built-in optional Windows component across client SKUs as well as Windows Server. Even if a standard office PC never hosts a public website, software developers, QA engineers, local intranet tools, and certain enterprise management agents routinely enable IIS components on Windows 10 and Windows 11 endpoints. Furthermore, Microsoft services core OS binaries through cumulative updates across each platform branch, ensuring that whether IIS is actively listening today or enabled six months from now via Windows Features, the underlying binaries are already hardened.
Notice also in the affected product matrix below that several newer branches—specifically Windows 11 Versions 24H2, 25H2, and 26H2, along with Windows Server 2025—list two distinct KB-to-build remediation paths, giving administrators exact target build numbers to verify depending on which servicing package applies to their deployment channel.
Section Summary: Both Windows Server installations (Full and Server Core) and Windows 10/11 client systems across x86, x64, and ARM64 architectures require the cumulative updates to ensure all IIS components are brought up to fixed builds.
Affected Products, KB Articles, and Fixed Build Mapping
Every affected platform listed in the MSRC advisory for CVE-2026-119961, together with its exact Knowledge Base (KB) package and vendor fixed build number, is detailed in the table below.
| Affected Product | KB Article(s) | Vendor Fixed Build(s) |
|---|---|---|
| Windows 10 Version 1607 for 32-bit Systems (x86) | KB5131291 | 10.0.14393.9688 |
| Windows 10 Version 1607 for x64-based Systems | KB5131291 | 10.0.14393.9688 |
| Windows 10 Version 1809 for 32-bit Systems (x86) | KB5131085 | 10.0.17763.9487 |
| Windows 10 Version 1809 for x64-based Systems | KB5131085 | 10.0.17763.9487 |
| Windows 10 Version 21H2 for 32-bit Systems (x86) | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 21H2 for ARM64-based Systems | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 21H2 for x64-based Systems | KB5131096 | 10.0.19044.7846 |
| Windows 10 Version 22H2 for 32-bit Systems (x86) | KB5131096 | 10.0.19045.7846 |
| Windows 10 Version 22H2 for ARM64-based Systems | KB5131096 | 10.0.19045.7846 |
| Windows 10 Version 22H2 for x64-based Systems | KB5131096 | 10.0.19045.7846 |
| Windows 11 Version 23H2 for ARM64-based Systems | KB5131087 | 10.0.22631.7711 |
| Windows 11 Version 23H2 for x64-based Systems | KB5131087 | 10.0.22631.7711 |
| Windows 11 Version 24H2 for ARM64-based Systems | KB5132043; KB5132061 | 10.0.26100.9911; 10.0.26100.9974 |
| Windows 11 Version 24H2 for x64-based Systems | KB5132043; KB5132061 | 10.0.26100.9911; 10.0.26100.9974 |
| Windows 11 Version 25H2 for ARM64-based Systems | KB5132043; KB5132061 | 10.0.26200.9911; 10.0.26200.9974 |
| Windows 11 Version 25H2 for x64-based Systems | KB5132043; KB5132061 | 10.0.26200.9911; 10.0.26200.9974 |
| Windows 11 Version 26H1 for ARM64-based Systems | KB5132059 | 10.0.28000.3501 |
| Windows 11 version 26H1 for x64-based Systems | KB5132059 | 10.0.28000.3501 |
| Windows 11 Version 26H2 for ARM64-based Systems | KB5132043; KB5132061 | 10.0.26300.9911; 10.0.26300.9974 |
| Windows 11 Version 26H2 for x64-based Systems | KB5132043; KB5132061 | 10.0.26300.9911; 10.0.26300.9974 |
| Windows Server 2016 (Server Core installation) (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2016 (x64) | KB5131291 | 10.0.14393.9688 |
| Windows Server 2019 (Server Core installation) (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2019 (x64) | KB5131085 | 10.0.17763.9487 |
| Windows Server 2022 (Server Core installation) (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2022 (x64) | KB5131090 | 10.0.20348.5870 |
| Windows Server 2025 (Server Core installation) (x64) | KB5131077; KB5131080 | 10.0.26100.33730; 10.0.26100.33822 |
| Windows Server 2025 (x64) | KB5131077; KB5131080 | 10.0.26100.33730; 10.0.26100.33822 |
Section Summary: Twenty-eight distinct Windows client and Windows Server product targets receive official security updates across ten KB packages to remediate CVE-2026-119961.
Official Remediation Directives and Admin Checklist
Because Customer action required: Yes applies to CVE-2026-119961, administrators should deploy the exact Microsoft security patches corresponding to each operating system in their inventory:
- For Windows 10 Version 1607 for 32-bit Systems (x86), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows 10 Version 1607 for x64-based Systems, install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows 10 Version 1809 for 32-bit Systems (x86), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows 10 Version 1809 for x64-based Systems, install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows 10 Version 21H2 for 32-bit Systems (x86), install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 21H2 for ARM64-based Systems, install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 21H2 for x64-based Systems, install KB5131096 to reach fixed build 10.0.19044.7846.
- For Windows 10 Version 22H2 for 32-bit Systems (x86), install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 10 Version 22H2 for ARM64-based Systems, install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 10 Version 22H2 for x64-based Systems, install KB5131096 to reach fixed build 10.0.19045.7846.
- For Windows 11 Version 23H2 for ARM64-based Systems, install KB5131087 to reach fixed build 10.0.22631.7711.
- For Windows 11 Version 23H2 for x64-based Systems, install KB5131087 to reach fixed build 10.0.22631.7711.
- For Windows 11 Version 24H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26100.9911; install KB5132061 to reach fixed build 10.0.26100.9974.
- For Windows 11 Version 24H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26100.9911; install KB5132061 to reach fixed build 10.0.26100.9974.
- For Windows 11 Version 25H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26200.9911; install KB5132061 to reach fixed build 10.0.26200.9974.
- For Windows 11 Version 25H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26200.9911; install KB5132061 to reach fixed build 10.0.26200.9974.
- For Windows 11 Version 26H1 for ARM64-based Systems, install KB5132059 to reach fixed build 10.0.28000.3501.
- For Windows 11 version 26H1 for x64-based Systems, install KB5132059 to reach fixed build 10.0.28000.3501.
- For Windows 11 Version 26H2 for ARM64-based Systems, install KB5132043 to reach fixed build 10.0.26300.9911; install KB5132061 to reach fixed build 10.0.26300.9974.
- For Windows 11 Version 26H2 for x64-based Systems, install KB5132043 to reach fixed build 10.0.26300.9911; install KB5132061 to reach fixed build 10.0.26300.9974.
- For Windows Server 2016 (Server Core installation) (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2016 (x64), install KB5131291 to reach fixed build 10.0.14393.9688.
- For Windows Server 2019 (Server Core installation) (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2019 (x64), install KB5131085 to reach fixed build 10.0.17763.9487.
- For Windows Server 2022 (Server Core installation) (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2022 (x64), install KB5131090 to reach fixed build 10.0.20348.5870.
- For Windows Server 2025 (Server Core installation) (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
- For Windows Server 2025 (x64), install KB5131077 to reach fixed build 10.0.26100.33730; install KB5131080 to reach fixed build 10.0.26100.33822.
Practical Deployment Priority for IT Teams
Drawing on standard enterprise patch management practices, teams balancing uptime against security exposure can stage their rollout sensibly:
- Prioritize Internet-Facing and DMZ IIS Hosts First: Any Windows Server 2016, 2019, 2022, or 2025 machine actively running IIS roles exposed to untrusted networks should sit at the front of the queue, followed closely by internal web application servers, PKI enrollment web endpoints, and management servers that rely on IIS.
- Audit Non-Standard Client IIS Installations: Developer laptops and test rigs running Windows 10 or Windows 11 with local IIS enabled should receive their cumulative updates promptly and have unnecessary firewall rules exposing IIS ports to corporate or guest Wi-Fi segments disabled.
- Verify Post-Reboot OS Build Numbers: Installing a KB package without completing the required system restart leaves running services using unpatched binaries in memory. Always verify compliance against the exact fixed build numbers listed above—and feel free to compare rollout notes in the WindowsForum.com security advisories and Windows Update troubleshooting discussions if any cumulative update gives a legacy server grief.
Section Summary: Applying the designated cumulative updates and verifying the resulting OS build numbers closes CVE-2026-119961 completely across Windows 10, Windows 11, and Windows Server environments before attackers have a chance to test their luck against the race condition.
References
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com