Abstract illustration of connected devices separated by a protected security boundary.
Microsoft’s CVE-2026-88216: Windows DHCP Server Remote Code Execution Vulnerability addresses a race condition that allows an authorized attacker to execute code over a network. Microsoft rates the vulnerability Important, with a CVSS base score of 7.5, and identifies fixes for the affected server installations listed below.

The key qualification is attack complexity: successful exploitation requires the attacker to win a race condition. That makes exploitation harder, but it does not remove the need to patch. Microsoft explicitly identifies customer action as required.

Abstract illustration of connected devices separated by a protected security boundary. What the vulnerability allows​

According to Microsoft’s advisory, a time-of-check time-of-use (TOCTOU) race condition in Windows DHCP Server permits network-based code execution by an authorized attacker.

In practical terms, a TOCTOU issue involves a gap between checking a condition and using the result. An attacker must exploit that timing window. Microsoft specifically explains that the high attack complexity metric, AC:H, reflects the requirement to win a race condition.

The advisory’s severity, scoring, and status details are:

FieldMicrosoft advisory value
CVECVE-2026-88216
Exact titleWindows DHCP Server Remote Code Execution Vulnerability
SeverityImportant
CVSS base score7.5
CVSS temporal score6.5
Weakness identifiersCWE-122; CWE-367
Exploitation assessmentExploitation Less Likely
  • Publicly disclosed: No
  • Exploited: No
  • Customer action required: Yes

Microsoft supplies the following complete CVSS vector:

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

The vector describes a network attack requiring low privileges and no user interaction, with high attack complexity and unchanged scope. It assigns high potential impact to confidentiality, integrity, and availability.

The operational takeaway: this is not described as an unauthenticated attack. Nevertheless, the combination of network reachability, no required user interaction, and potential code execution makes it a meaningful server security update. “Exploitation Less Likely” is a prioritization input—not a substitute for remediation.

Affected products and exact remediation​

Microsoft’s affected-product records include both Server Core and other listed installations. The following instructions preserve the exact product names, KB identifiers, and vendor fixed builds.

Server generation 2016​

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

Server generation 2019​

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

Server generation 2022​

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

Server generation 2025​

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

What administrators should verify​

A useful comparison emerges from Microsoft’s mappings: Server Core and the other listed installation share the same KB-to-build mapping within each server generation. Server Core therefore belongs in the same remediation inventory for this vulnerability; excluding it would leave explicitly affected products outside the patch plan.

The newest listed generation also has two distinct KB-to-build mappings. That matters when validating deployment results: each KB should be associated with its own listed fixed build, rather than treating both updates as producing the same version.

Based on those records, a practical verification workflow is:

  1. Identify affected hosts. Match the server generation, installation type, and architecture against the exact product entries above, with attention to systems providing Windows DHCP Server.
  2. Assign the matching remediation. Use Microsoft’s product-specific KB and fixed-build pairing rather than a single update identifier across the fleet.
  3. Validate deployment results. Compare the recorded update and resulting build with the corresponding mapping. A deployment job marked complete should not be the only evidence used to close the remediation task.
  4. Keep installation types in scope. Review Server Core hosts alongside the other affected installations.

These are operational recommendations derived from the advisory’s affected-product and remediation data, not additional exploitation claims.

Bottom line​

CVE-2026-88216 combines a substantial potential impact with meaningful attack constraints: an authorized attacker must win a race condition, and Microsoft assesses exploitation as less likely. The response should be measured but concrete—apply the matching security update and verify the fixed build across every affected installation type.

 

References

  1. Official MSRC or vendor evidence api.msrc.microsoft.com
  2. Official MSRC or vendor evidence msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com