CVE-2026-45602

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

No cwe for this issue in Windows DHCP Server allows an unauthorized attacker to perform tampering over a network.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Aug 1, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45602

Vendor Advisories for CVE-2026-45602(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 40× in last 7d / 255× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 620 total refreshes for this CVE.

  1. 2026-08-25 23:04 UTCEG score recompute
  2. 2026-08-25 23:04 UTCVendor advisory
  3. 2026-08-25 23:04 UTCGHSA enrichment
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 05:10 UTCGHSA enrichment
  6. 2026-08-25 00:50 UTCVendor advisory
  7. 2026-08-25 00:50 UTCGHSA enrichment
  8. 2026-08-24 15:37 UTCEG score recompute
  9. 2026-08-24 15:37 UTCVendor advisory
  10. 2026-08-24 15:37 UTCGHSA enrichment
  11. 2026-08-24 00:10 UTCVendor advisory
  12. 2026-08-24 00:10 UTCGHSA enrichment
  13. 2026-08-23 19:49 UTCVendor advisory
  14. 2026-08-23 19:49 UTCGHSA enrichment
  15. 2026-08-23 15:29 UTCVendor advisory
  16. 2026-08-23 15:29 UTCGHSA enrichment
  17. 2026-08-23 11:09 UTCEG score recompute
  18. 2026-08-23 11:09 UTCGHSA enrichment
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-22 00:05 UTCEG score recompute
  21. 2026-08-22 00:05 UTCVendor advisory
  22. 2026-08-22 00:05 UTCGHSA enrichment
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 19:45 UTCGHSA enrichment
  25. 2026-08-21 12:23 UTCVendor advisory
Show 75 more
  1. 2026-08-21 12:23 UTCGHSA enrichment
  2. 2026-08-21 06:38 UTCVendor advisory
  3. 2026-08-21 06:38 UTCGHSA enrichment
  4. 2026-08-21 02:11 UTCEG score recompute
  5. 2026-08-21 02:11 UTCVendor advisory
  6. 2026-08-21 02:11 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 21:45 UTCVendor advisory
  9. 2026-08-20 21:45 UTCGHSA enrichment
  10. 2026-08-20 17:25 UTCVendor advisory
  11. 2026-08-20 17:25 UTCGHSA enrichment
  12. 2026-08-20 08:59 UTCEG score recompute
  13. 2026-08-20 08:59 UTCVendor advisory
  14. 2026-08-20 08:59 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 13:20 UTCVendor advisory
  19. 2026-08-17 13:20 UTCGHSA enrichment
  20. 2026-08-17 09:00 UTCVendor advisory
  21. 2026-08-17 09:00 UTCGHSA enrichment
  22. 2026-08-17 04:41 UTCVendor advisory
  23. 2026-08-17 04:41 UTCGHSA enrichment
  24. 2026-08-17 00:21 UTCEG score recompute
  25. 2026-08-17 00:21 UTCVendor advisory
  26. 2026-08-17 00:21 UTCGHSA enrichment
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 14:14 UTCVendor advisory
  29. 2026-08-16 14:14 UTCGHSA enrichment
  30. 2026-08-16 09:12 UTCVendor advisory
  31. 2026-08-16 09:12 UTCGHSA enrichment
  32. 2026-08-16 04:50 UTCEG score recompute
  33. 2026-08-16 04:50 UTCVendor advisory
  34. 2026-08-16 04:50 UTCGHSA enrichment
  35. 2026-08-16 02:14 UTCEPSS rescore
  36. 2026-08-16 00:30 UTCVendor advisory
  37. 2026-08-16 00:30 UTCGHSA enrichment
  38. 2026-08-15 15:45 UTCVendor advisory
  39. 2026-08-15 15:45 UTCGHSA enrichment
  40. 2026-08-15 11:25 UTCVendor advisory
  41. 2026-08-15 11:25 UTCGHSA enrichment
  42. 2026-08-15 06:00 UTCEG score recompute
  43. 2026-08-15 06:00 UTCVendor advisory
  44. 2026-08-15 06:00 UTCGHSA enrichment
  45. 2026-08-15 01:30 UTCEPSS rescore
  46. 2026-08-15 01:12 UTCVendor advisory
  47. 2026-08-15 01:12 UTCGHSA enrichment
  48. 2026-08-14 20:53 UTCVendor advisory
  49. 2026-08-14 20:53 UTCGHSA enrichment
  50. 2026-08-14 16:33 UTCVendor advisory
  51. 2026-08-14 16:33 UTCGHSA enrichment
  52. 2026-08-14 14:19 UTCVendor advisory
  53. 2026-08-14 14:19 UTCGHSA enrichment
  54. 2026-08-14 09:59 UTCVendor advisory
  55. 2026-08-14 09:59 UTCGHSA enrichment
  56. 2026-08-14 05:39 UTCVendor advisory
  57. 2026-08-14 05:39 UTCGHSA enrichment
  58. 2026-08-14 01:19 UTCEG score recompute
  59. 2026-08-14 01:19 UTCVendor advisory
  60. 2026-08-14 01:19 UTCGHSA enrichment
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-13 20:59 UTCVendor advisory
  63. 2026-08-13 20:59 UTCGHSA enrichment
  64. 2026-08-13 14:56 UTCVendor advisory
  65. 2026-08-13 14:56 UTCGHSA enrichment
  66. 2026-08-13 10:04 UTCVendor advisory
  67. 2026-08-13 10:04 UTCGHSA enrichment
  68. 2026-08-13 05:43 UTCVendor advisory
  69. 2026-08-13 05:43 UTCGHSA enrichment
  70. 2026-08-13 00:58 UTCGHSA enrichment
  71. 2026-08-12 20:39 UTCVendor advisory
  72. 2026-08-12 20:39 UTCGHSA enrichment
  73. 2026-08-12 16:19 UTCEG score recompute
  74. 2026-08-12 16:19 UTCVendor advisory
  75. 2026-08-12 16:19 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-45602?
CVE-2026-45602 is a critical vulnerability published on June 9, 2026. No cwe for this issue in Windows DHCP Server allows an unauthorized attacker to perform tampering over a network.
When was CVE-2026-45602 disclosed?
CVE-2026-45602 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45602 actively exploited?
CVE-2026-45602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45602?
CVE-2026-45602 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45602, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45602

Explore →

Is Your Infrastructure Affected by CVE-2026-45602?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.