CVE-2026-45602

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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

July 20, 2026

Advisory Details (1)

Auto-updated Jun 9, 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 16× in last 7d / 179× 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 367 total refreshes for this CVE.

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

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 July 20, 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-45602?
CVE-2026-45602 has a CVSS v3 base score of 9.1 (NVD).
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.