CVE-2026-69416

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreHIGH confidence

Score 5.7 from GitHub Security Advisory published 2026-09-08. the CNA's CVSS baseline 5.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.7Exploit: None knownExposed: 0

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

Buffer over-read in Windows DHCP Server allows an authorized attacker to deny service over an adjacent network.

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

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-69416

Vendor Advisories for CVE-2026-69416(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 36× in last 7d / 70× 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.

  1. 2026-09-19 19:18 UTCEG score recompute
  2. 2026-09-19 19:18 UTCVendor advisory
  3. 2026-09-19 19:18 UTCGHSA enrichment
  4. 2026-09-18 21:02 UTCEG score recompute
  5. 2026-09-18 21:02 UTCVendor advisory
  6. 2026-09-18 21:02 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 14:10 UTCVendor advisory
  9. 2026-09-18 14:10 UTCGHSA enrichment
  10. 2026-09-17 23:39 UTCVendor advisory
  11. 2026-09-17 23:39 UTCGHSA enrichment
  12. 2026-09-17 20:10 UTCEG score recompute
  13. 2026-09-17 20:10 UTCVendor advisory
  14. 2026-09-17 20:10 UTCGHSA enrichment
  15. 2026-09-17 15:29 UTCEG score recompute
  16. 2026-09-17 15:29 UTCVendor advisory
  17. 2026-09-17 15:29 UTCGHSA enrichment
  18. 2026-09-16 22:01 UTCVendor advisory
  19. 2026-09-16 22:01 UTCGHSA enrichment
  20. 2026-09-16 21:16 UTCEG score recompute
  21. 2026-09-16 21:16 UTCVendor advisory
  22. 2026-09-16 21:16 UTCGHSA enrichment
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 23:04 UTCVendor advisory
Show 45 more
  1. 2026-09-15 23:04 UTCGHSA enrichment
  2. 2026-09-15 17:55 UTCEG score recompute
  3. 2026-09-15 17:55 UTCVendor advisory
  4. 2026-09-15 17:55 UTCGHSA enrichment
  5. 2026-09-14 23:13 UTCVendor advisory
  6. 2026-09-14 23:13 UTCGHSA enrichment
  7. 2026-09-14 17:44 UTCVendor advisory
  8. 2026-09-14 17:44 UTCGHSA enrichment
  9. 2026-09-13 19:16 UTCEG score recompute
  10. 2026-09-13 19:16 UTCVendor advisory
  11. 2026-09-13 19:16 UTCGHSA enrichment
  12. 2026-09-12 21:05 UTCEG score recompute
  13. 2026-09-12 21:05 UTCVendor advisory
  14. 2026-09-12 21:05 UTCGHSA enrichment
  15. 2026-09-11 22:55 UTCVendor advisory
  16. 2026-09-11 22:55 UTCGHSA enrichment
  17. 2026-09-11 20:04 UTCVendor advisory
  18. 2026-09-11 20:04 UTCGHSA enrichment
  19. 2026-09-11 16:53 UTCEG score recompute
  20. 2026-09-11 16:53 UTCVendor advisory
  21. 2026-09-11 16:53 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 23:33 UTCGHSA enrichment
  25. 2026-09-10 20:12 UTCEG score recompute
  26. 2026-09-10 20:12 UTCGHSA enrichment
  27. 2026-09-09 22:01 UTCGHSA enrichment
  28. 2026-09-09 20:04 UTCVendor advisory
  29. 2026-09-09 20:04 UTCGHSA enrichment
  30. 2026-09-09 00:05 UTCEG score recompute
  31. 2026-09-09 00:05 UTCVendor advisory
  32. 2026-09-09 00:04 UTCGHSA enrichment
  33. 2026-09-08 21:47 UTCEG score recompute
  34. 2026-09-08 21:47 UTCVendor advisory
  35. 2026-09-08 21:47 UTCGHSA enrichment
  36. 2026-09-08 20:55 UTCEG score recompute
  37. 2026-09-08 20:55 UTCGHSA enrichment
  38. 2026-09-08 19:40 UTCEG score recompute
  39. 2026-09-08 19:39 UTCGHSA enrichment
  40. 2026-09-08 18:48 UTCEG score recompute
  41. 2026-09-08 18:48 UTCVendor advisory
  42. 2026-09-08 18:48 UTCGHSA enrichment
  43. 2026-09-08 17:52 UTCEG score recompute
  44. 2026-09-08 17:52 UTCVendor advisory
  45. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69416?
CVE-2026-69416 is a medium vulnerability published on September 8, 2026. Buffer over-read in Windows DHCP Server allows an authorized attacker to deny service over an adjacent network.
When was CVE-2026-69416 disclosed?
CVE-2026-69416 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69416 actively exploited?
CVE-2026-69416 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 54.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69416?
CVE-2026-69416 has a CVSS v4.0 base score of 5.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69416, 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-69416

Explore →

Is Your Infrastructure Affected by CVE-2026-69416?

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

Start Free Scan →Browse All CVEs