Skip to content
major vulnerability· requires attention

Affects Windows Server DHCP service widely deployed across enterprises; RCE against core network service can disrupt corporate networks and operations.

Infrastructure

CVE-2026-62823

8.8
High
EPSS 0.66%Patch availableAug 12, 2026

Heap overflow in Windows DHCP Server allows adjacent-network remote code execution.

common questions

Is CVE-2026-62823 being exploited?

Not confirmed. CVE-2026-62823 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.

How severe is CVE-2026-62823?

CVE-2026-62823 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62823?

Yes. A fix has been recorded for CVE-2026-62823. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62823 affect?

CVE-2026-62823 affects Microsoft Windows Server DHCP service (DHCP role), Windows Server installations running DHCP role. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62823?

Isolate DHCP servers, apply vendor patch ASAP, restrict DHCP access and monitor logs/IDS/EDR.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Microsoft Windows Server DHCP service (DHCP role)Windows Server installations running DHCP role
impact

Remote code execution as SYSTEM via heap overflow in Windows DHCP Server from an adjacent network, enabling takeover, malware deployment, and persistent access.

action required

Immediate action required

affected versions
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.26280
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.23338
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.23338
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.26280
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.9418
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.9418
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9121
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9121
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5499
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33296
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33296

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free