CVE-2026-69629

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. 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 Microsoft Office Outlook allows an unauthorized attacker to execute code over a 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
56%
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-69629

Vendor Advisories for CVE-2026-69629(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 47× in last 7d / 96× 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-21 01:39 UTCEG score recompute
  2. 2026-09-21 01:39 UTCVendor advisory
  3. 2026-09-21 01:39 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 12:29 UTCVendor advisory
  6. 2026-09-20 12:29 UTCGHSA enrichment
  7. 2026-09-19 23:16 UTCEG score recompute
  8. 2026-09-19 23:16 UTCVendor advisory
  9. 2026-09-19 23:16 UTCGHSA enrichment
  10. 2026-09-19 10:06 UTCVendor advisory
  11. 2026-09-19 10:06 UTCGHSA enrichment
  12. 2026-09-18 20:57 UTCEG score recompute
  13. 2026-09-18 20:57 UTCVendor advisory
  14. 2026-09-18 20:57 UTCGHSA enrichment
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 14:06 UTCVendor advisory
  17. 2026-09-18 14:06 UTCGHSA enrichment
  18. 2026-09-18 12:38 UTCVendor advisory
  19. 2026-09-18 12:38 UTCGHSA enrichment
  20. 2026-09-17 23:28 UTCVendor advisory
  21. 2026-09-17 23:28 UTCGHSA enrichment
  22. 2026-09-17 20:07 UTCEG score recompute
  23. 2026-09-17 20:07 UTCVendor advisory
  24. 2026-09-17 20:07 UTCGHSA enrichment
  25. 2026-09-17 14:31 UTCVendor advisory
Show 71 more
  1. 2026-09-17 14:31 UTCGHSA enrichment
  2. 2026-09-17 01:15 UTCEG score recompute
  3. 2026-09-17 01:15 UTCVendor advisory
  4. 2026-09-17 01:15 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 12:05 UTCEG score recompute
  7. 2026-09-16 12:05 UTCVendor advisory
  8. 2026-09-16 12:05 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 22:55 UTCVendor advisory
  11. 2026-09-15 22:55 UTCGHSA enrichment
  12. 2026-09-15 17:51 UTCVendor advisory
  13. 2026-09-15 17:51 UTCGHSA enrichment
  14. 2026-09-15 12:17 UTCEG score recompute
  15. 2026-09-15 12:17 UTCVendor advisory
  16. 2026-09-15 12:17 UTCGHSA enrichment
  17. 2026-09-14 23:07 UTCVendor advisory
  18. 2026-09-14 23:07 UTCGHSA enrichment
  19. 2026-09-14 17:37 UTCVendor advisory
  20. 2026-09-14 17:37 UTCGHSA enrichment
  21. 2026-09-14 16:27 UTCVendor advisory
  22. 2026-09-14 16:27 UTCGHSA enrichment
  23. 2026-09-14 03:16 UTCEG score recompute
  24. 2026-09-14 03:16 UTCVendor advisory
  25. 2026-09-14 03:16 UTCGHSA enrichment
  26. 2026-09-13 14:07 UTCVendor advisory
  27. 2026-09-13 14:07 UTCGHSA enrichment
  28. 2026-09-13 00:57 UTCEG score recompute
  29. 2026-09-13 00:57 UTCVendor advisory
  30. 2026-09-13 00:57 UTCGHSA enrichment
  31. 2026-09-12 11:47 UTCVendor advisory
  32. 2026-09-12 11:47 UTCGHSA enrichment
  33. 2026-09-11 22:37 UTCVendor advisory
  34. 2026-09-11 22:36 UTCGHSA enrichment
  35. 2026-09-11 19:59 UTCVendor advisory
  36. 2026-09-11 19:59 UTCGHSA enrichment
  37. 2026-09-11 16:59 UTCEG score recompute
  38. 2026-09-11 16:59 UTCVendor advisory
  39. 2026-09-11 16:59 UTCGHSA enrichment
  40. 2026-09-11 14:53 UTCEPSS rescore
  41. 2026-09-11 12:38 UTCEG score recompute
  42. 2026-09-11 12:37 UTCGHSA enrichment
  43. 2026-09-11 09:37 UTCEPSS rescore
  44. 2026-09-10 23:26 UTCGHSA enrichment
  45. 2026-09-10 10:59 UTCEG score recompute
  46. 2026-09-10 10:59 UTCGHSA enrichment
  47. 2026-09-09 21:49 UTCGHSA enrichment
  48. 2026-09-09 20:01 UTCEG score recompute
  49. 2026-09-09 20:01 UTCVendor advisory
  50. 2026-09-09 20:01 UTCGHSA enrichment
  51. 2026-09-09 19:30 UTCVendor advisory
  52. 2026-09-09 19:30 UTCGHSA enrichment
  53. 2026-09-09 10:27 UTCEG score recompute
  54. 2026-09-09 10:27 UTCVendor advisory
  55. 2026-09-09 10:27 UTCGHSA enrichment
  56. 2026-09-09 10:02 UTCVendor advisory
  57. 2026-09-09 10:02 UTCGHSA enrichment
  58. 2026-09-09 04:30 UTCVendor advisory
  59. 2026-09-09 04:30 UTCGHSA enrichment
  60. 2026-09-09 04:05 UTCEG score recompute
  61. 2026-09-09 04:05 UTCVendor advisory
  62. 2026-09-09 04:04 UTCGHSA enrichment
  63. 2026-09-08 23:56 UTCEG score recompute
  64. 2026-09-08 23:56 UTCVendor advisory
  65. 2026-09-08 23:56 UTCGHSA enrichment
  66. 2026-09-08 18:40 UTCEG score recompute
  67. 2026-09-08 18:40 UTCVendor advisory
  68. 2026-09-08 18:40 UTCGHSA enrichment
  69. 2026-09-08 17:45 UTCEG score recompute
  70. 2026-09-08 17:45 UTCVendor advisory
  71. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69629?

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

Start Free Scan →Browse All CVEs