Windows NAT After CVE-2026-113862: High Complexity Is Not Low Risk
CVE-2026-113862 is a remote code execution bug in Windows Network Address Translation. Microsoft describes a use-after-free that allows an unauthorized attacker to execute code over a network. The CVSS 3.1 score is 8.1, with network access, high attack complexity, no privileges, and no user interaction.
High complexity means the attacker must control timing, state, or other conditions instead of sending a single reliable request. It does not mean the issue is theoretical. NAT runs at a trust boundary in Windows hosts, servers, virtual networks, remote-access paths, and container or virtualization deployments. A memory corruption bug in that component can affect traffic processing before an application-level control makes a decision.
Affected surface
Microsoft's affected-product data covers Windows 10, Windows 11, Windows Server 2016 through 2025, and related Server Core installations. The exact fixed build depends on the Windows release. The vulnerability is remotely reachable, so a host that does not expose NAT should not be treated the same as an internet-facing gateway or a virtualization host forwarding tenant traffic.
The advisory describes the impact at the component level. It does not publish a packet-level exploit or prove that every NAT configuration is reachable. Teams need to map where the Windows NAT service is enabled and which interfaces it processes.
Build a NAT inventory
Collect Windows build numbers and installed updates from:
- Remote-access and VPN gateways.
- Windows hosts running containers or virtual networking.
- Hyper-V and virtualization management nodes.
- Edge appliances or jump hosts that forward traffic between trust zones.
- Test and recovery environments that clone production network configuration.
A version scanner can miss a host if NAT is enabled in a role or feature that is not part of the normal server inventory. Configuration management should record enabled Windows features, network interfaces, forwarding rules, and listening services.
Prioritize and verify
Install the November 2026 cumulative update that contains the fixed build for each Windows release. Reboot and verify the running build. For hosts where the update cannot be applied immediately, reduce exposure by removing unnecessary NAT rules and restricting the interfaces that can reach the NAT engine. Network filtering can lower reachability but does not repair the memory bug.
After the reboot, test from the expected untrusted network segment. Confirm that the host is not unintentionally forwarding traffic from an interface that should not reach NAT. Review firewall rules for stale exceptions tied to old application tests.
For incident response, capture packet flows, NAT state, Windows event logs, crash dumps, and process trees. Memory corruption in a kernel or network component may leave limited application evidence. Compare a sudden reset, bug check, or unusual outbound connection from a NAT host with network flow records before drawing a conclusion.
The security decision is not "high complexity, so defer." It is "find every exposed NAT boundary, patch the ones with the least trusted reach, and verify that the intended interface policy still holds."