CVE-2026-62823

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.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: 8.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 an adjacent network.

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

Published

August 11, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62823

Vendor Advisories for CVE-2026-62823(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 86× in last 7d / 127× 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 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62823?
CVE-2026-62823 is a high vulnerability published on August 11, 2026. Heap-based buffer overflow in Windows DHCP Server allows an unauthorized attacker to execute code over an adjacent network.
When was CVE-2026-62823 disclosed?
CVE-2026-62823 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 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-62823 actively exploited?
CVE-2026-62823 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 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-62823?
CVE-2026-62823 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62823, 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-62823

Explore →

Is Your Infrastructure Affected by CVE-2026-62823?

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

Start Free Scan →Browse All CVEs