CVE-2026-58627

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. the CNA's CVSS baseline 7.5; sources differ by 0.0.

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

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

Uncontrolled resource consumption in Windows DHCP Server allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jul 15, 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-58627

Vendor Advisories for CVE-2026-58627(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 166× 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 245 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58627?
CVE-2026-58627 is a high vulnerability published on July 14, 2026. Uncontrolled resource consumption in Windows DHCP Server allows an unauthorized attacker to deny service over a network.
When was CVE-2026-58627 disclosed?
CVE-2026-58627 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58627 actively exploited?
CVE-2026-58627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.2% of all scored CVEs.
What is the CVSS score of CVE-2026-58627?
CVE-2026-58627 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-58627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58627, 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-58627

Explore →

Is Your Infrastructure Affected by CVE-2026-58627?

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