CVE-2026-50518

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

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

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

Heap-based buffer overflow in Windows DHCP Server allows an unauthorized attacker to execute code over a network.

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

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 28, 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-50518

Vendor Advisories for CVE-2026-50518(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 63× in last 7d / 375× 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 504 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50518?
CVE-2026-50518 is a critical vulnerability published on July 14, 2026. Heap-based buffer overflow in Windows DHCP Server allows an unauthorized attacker to execute code over a network.
When was CVE-2026-50518 disclosed?
CVE-2026-50518 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-50518 actively exploited?
CVE-2026-50518 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 40.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50518?
CVE-2026-50518 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50518?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50518, 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-50518

Explore →

Is Your Infrastructure Affected by CVE-2026-50518?

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

Start Free Scan →Browse All CVEs