CVE-2026-62804

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

External control of file name or path 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
26%
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-62804

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62804?

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

Start Free Scan →Browse All CVEs