IT SBIT Services
Schneeberger
DEEN
CVE tracker

Microsoft Windows: Remote code execution in RPC Runtime

CVE-2026-102203High 8.8

← All vulnerabilities

Summary

A type confusion flaw in the Windows RPC Runtime component affects multiple Windows client and server editions, including Windows 10 1607. An unauthenticated remote attacker can execute code over the network if a user interacts with a crafted request or resource. The CVSS base score is 8.8 (High). Microsoft's CNA record gives no exploitation status beyond the CISA SSVC assessment (exploitation: none, automatable: no, technical impact: total).

Affected

  • Windows 10 Version 1607 (builds 10.0.14393.0 to below 10.0.14393.9612)
  • Windows 10 Version 1809 (builds below 10.0.17763.9376)
  • Windows 10 Version 21H2 (builds below 10.0.19044.7807)
  • Windows 10 Version 22H2 (builds below 10.0.19045.7807)
  • Windows 11 Version 23H2 (builds below 10.0.22631.7652)
  • Windows 11 Version 24H2 (builds below 10.0.26100.9711)
  • Windows 11 Version 25H2 (builds below 10.0.26200.9711)
  • Windows 11 Version 26H1 (builds below 10.0.28000.3231)
  • Windows 11 Version 26H2 (builds below 10.0.26300.9711)
  • Windows Server 2012 and Server Core installation (builds below 6.2.9200.26434)
  • Windows Server 2012 R2 and Server Core installation (builds below 6.3.9600.23470)
  • Windows Server 2016 (builds below 10.0.14393.9612)

Note: the CPE in the source data lists only Windows 10 1607; the CNA record lists the products above.

Fixed in

  • Install the October 2026 security updates from Microsoft (the fixed builds are listed in the affected section).
  • Windows 10 1607 / Server 2016: build 10.0.14393.9612 or later.
  • Windows 10 1607 KB number: Unknown.
  • Verify the fixed builds and KB numbers on the Microsoft Security Update Guide before deployment.

Workaround

  • No official Microsoft workaround confirmed.
  • Generic mitigation (not Microsoft guidance): block RPC traffic from untrusted networks at firewalls and review firewall rules for RPC.

Exploitation

  • No evidence of exploitation in the wild found; not listed in CISA KEV at the time of research.
  • No public proof-of-concept found for this CVE.
  • A Tenable plugin for the October update references this CVE with an exploit flag, but this flag applies to the update as a whole and does not confirm a PoC.
  • CISA SSVC: exploitation none, not automatable.

Our recommendation

  • Inventory all Windows systems and identify affected builds, including any Windows 10 1607 hosts.
  • Patch affected systems first where RPC is reachable from untrusted networks, then apply the October 2026 updates in the normal cycle.
  • Block RPC access from the internet and untrusted network segments.
  • Monitor logs for unusual RPC traffic.
  • Check the Microsoft lifecycle for Windows 10 1607; if no fix is available, plan an upgrade.

Information from Microsoft (Patch Tuesday October 2026)

Severity (Microsoft)
Important
Impact
Remote code execution – RPC Runtime
Status on Patch Tuesday
Neither exploited nor publicly disclosed
Exploitability assessment
Exploitation less likely
Product family
Windows, Windows ESU (Extended Security Updates)
Updates (KB)
KB5126835, KB5126836, KB5126868, KB5126651, KB5126657, KB5126655

Entry in the Microsoft Security Update Guide

Public exploits

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 19:35.

Original description (NVD)

Access of resource using incompatible type ('type confusion') in RPC Runtime allows an unauthorized attacker to execute code over a network.

NVD references (1)

Sources

The tracker combines official, freely usable data sources – updated continuously:

This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.

Affected? We can help.

We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.