Widely-used Windows DHCP Server; network-based tampering could enable MITM, IP spoofing, or service disruption across many networks.
CVE-2026-45602
Unauthorized DHCP tampering in Windows DHCP Server via network.
Is CVE-2026-45602 being exploited?
Not confirmed. CVE-2026-45602 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-45602?
CVE-2026-45602 is rated Critical with a CVSS score of 9.1. 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-45602?
Yes. A fix has been recorded for CVE-2026-45602. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45602 affect?
CVE-2026-45602 affects Windows DHCP Server (Windows Server). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45602?
Patch when available; enforce DHCP security controls; monitor for DHCP tampering.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated network tampering of DHCP messages enabling IP misallocation, redirection, MITM, or disruption.
Immediate action required
- affected>= 10.0.14393.0 and < 10.0.14393.9234
- affected>= 10.0.17763.0 and < 10.0.17763.8880
- affected>= 10.0.19044.0 and < 10.0.19044.7417
- affected>= 10.0.19045.0 and < 10.0.19045.7417
- affected>= 10.0.22631.0 and < 10.0.22631.7219
- affected>= 10.0.22631.0 and < 10.0.22631.7219
- affected>= 10.0.26100.0 and < 10.0.26100.8655
- affected>= 10.0.26200.0 and < 10.0.26200.8655
- affected>= 10.0.28000.0 and < 10.0.28000.2269
- affected>= 6.2.9200.0 and < 6.2.9200.26132
- affected>= 6.3.9600.0 and < 6.3.9600.23228
- affected>= 6.3.9600.0 and < 6.3.9600.23228
- affected>= 6.2.9200.0 and < 6.2.9200.26132
- affected>= 10.0.14393.0 and < 10.0.14393.9234
- affected>= 10.0.14393.0 and < 10.0.14393.9234
- affected>= 10.0.17763.0 and < 10.0.17763.8880
- affected>= 10.0.17763.0 and < 10.0.17763.8880
- affected>= 10.0.20348.0 and < 10.0.20348.5256
- affected>= 10.0.26100.0 and < 10.0.26100.32995
- affected>= 10.0.26100.0 and < 10.0.26100.32995
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.