CVE-2026-44817

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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.

Access of resource using incompatible type ('type confusion') in Microsoft Office Excel 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
30%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 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-44817

Vendor Advisories for CVE-2026-44817(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 20× in last 7d / 95× 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 186 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44817?
CVE-2026-44817 is a high vulnerability published on June 9, 2026. Access of resource using incompatible type ('type confusion') in Microsoft Office Excel allows an unauthorized attacker to execute code locally.
When was CVE-2026-44817 disclosed?
CVE-2026-44817 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44817 actively exploited?
CVE-2026-44817 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 70.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44817?
CVE-2026-44817 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-44817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44817, 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-44817

Explore →

Is Your Infrastructure Affected by CVE-2026-44817?

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