CVE-2026-64907

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. 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.

Stack-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code locally.

CVSS v3
7.8
EG Score
7.8(high)
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
27%
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-64907

Vendor Advisories for CVE-2026-64907(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 88× in last 7d / 129× 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 129 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64907?

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

Start Free Scan →Browse All CVEs