On this page (6 sections)

CVE-2026-88243 is a critical vulnerability in Windows DHCP Server. According to the NVD entry, an out-of-bounds read allows an unauthorized attacker to execute code over a network. The record was published on 2026-11-10 with a CVSS score of 9.8.

If you run the DHCP Server role on Windows Server, or manage someone who does, this belongs on your patching list. Public detail is very limited: the research for this article found only the NVD record and its reference to Microsoft's update guide. Below we separate what is confirmed from what is not.

What is known so far

The NVD description is a single sentence: an out-of-bounds read in Windows DHCP Server lets an unauthorized attacker execute code over a network. The CVE record lists a CVSS score of 9.8 and a critical rating, and its only reference is Microsoft's update guide entry. We found no second source that corroborates or expands on these details.

What the research does not tell us matters just as much. It does not list affected Windows versions, a fixed build or KB number, a CVSS vector string, or whether anyone is exploiting the flaw. The CVE record has no CISA Known Exploited Vulnerabilities entry. That is not evidence that the flaw is unexploited or safe to leave unpatched; it only means exploitation is unconfirmed.

The weakness in plain terms

CWE-125 is the class for reading memory outside the bounds of a buffer. As general background (not a finding from the advisory), it typically happens when a program trusts a length or offset taken from input without checking it. Out-of-bounds reads are commonly associated with information leaks or crashes, but here the CVE description states the impact is code execution. Until Microsoft's advisory says otherwise, treat it as more serious than a simple denial of service.

The wording 'unauthorized attacker' usually indicates that no authentication is required, and 'over a network' that no local access is needed. Confirm both in Microsoft's advisory, since the NVD text is only one sentence. Which network paths can reach the vulnerable code is not covered by the research, so do not assume either way.

Who is realistically exposed

  • Organizations running the DHCP Server role on Windows Server, including branch-office servers that are easy to forget.
  • Hosting providers and agencies that manage Windows servers for clients, where DHCP may serve office, lab or management networks.
  • Networks where less trusted devices (guest Wi-Fi, flat office networks, shared segments) can send traffic to the DHCP service.

As general background, DHCP is normally an internal service and is not usually meant to be reachable from the internet, which would lower the odds of mass external attacks. The research does not say how the flaw is reached, so a compromised workstation or rogue device on the same network segment is a reasonable scenario to plan for. Verify rather than assume.

How to check your exposure

First find out whether the role is installed. This read-only PowerShell command, run in an elevated session on a Windows Server machine, shows whether the DHCP Server feature is installed. Look for an install state of Installed.

Check whether the DHCP Server role is installed (run on each Windows Server, elevated PowerShell)PowerShell
Get-WindowsFeature -Name DHCP

Next, confirm the service state. This read-only command shows whether the DHCP Server service is present and running. A status of Running means the server is actively in service.

Check the DHCP Server service status (run on the server, PowerShell)PowerShell
Get-Service -Name DHCPServer

Then record the installed updates so you can compare against the fix once Microsoft's advisory names it. This read-only command lists the 15 most recent hotfixes, newest first.

List installed updates, newest first (run on the server, PowerShell)PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 15

What to do now

  1. Inventory every Windows Server with the DHCP Server role, including branch-office servers.
  2. Open Microsoft's advisory for CVE-2026-88243 and note the affected versions and the update that fixes each one.
  3. Test and deploy the fixing update, starting with DHCP servers reachable from the least trusted network segments.
  4. Restrict access to the DHCP service to the network segments that need it, and confirm it is not reachable from the internet.
  5. If the role is installed but unused, plan to remove it so there is nothing left to attack.
  6. Record patch dates and affected hosts so you can show the exposure window was closed.
Caution. Installing Windows updates on a DHCP server may require a restart, which interrupts address leasing for new clients. Schedule a maintenance window, and if you run DHCP failover, patch one partner at a time so clients keep getting leases.

Detection and monitoring

The research gives no indicators of compromise or exploitation details, so there is no specific signature to hunt for. Reasonable general steps are to watch DHCP servers for unexpected service crashes or restarts, review the Windows event logs for repeated DHCP Server service faults, and alert on unexpected new processes on DHCP hosts. Recheck the Microsoft advisory and the CISA KEV catalog for any change in exploitation status.

For broader guidance on keeping servers and networks patched and monitored, see our small business website security guide and the Webforta security blog for other Windows advisories.

Affected versions, fixed builds and exploitation status for CVE-2026-88243 are unconfirmed in the research. Treat this article as provisional until Microsoft's advisory details are checked.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-88243: Out-of-bounds read in Windows DHCP Server allows an unauthorized attacker to execute code over a network.nvd.nist.gov ·
  • Windows
  • DHCP
  • CVE-2026-88243
  • RCE
  • Patch management