CVE-2026-55017

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.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 allows an unauthorized attacker to execute code locally.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
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-55017

Vendor Advisories for CVE-2026-55017(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 31× in last 7d / 167× 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 236 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55017?
CVE-2026-55017 is a high vulnerability published on July 14, 2026. Heap-based buffer overflow in Microsoft Office allows an unauthorized attacker to execute code locally.
When was CVE-2026-55017 disclosed?
CVE-2026-55017 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-55017 actively exploited?
CVE-2026-55017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.5% of all scored CVEs.
What is the CVSS score of CVE-2026-55017?
CVE-2026-55017 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-55017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55017, 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-55017

Explore →

Is Your Infrastructure Affected by CVE-2026-55017?

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

Start Free Scan →Browse All CVEs