CVE-2026-44824

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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(high)
EPSS
36.4%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 1, 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-44824

Vendor Advisories for CVE-2026-44824(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 39× in last 7d / 181× 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 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44824?
CVE-2026-44824 is a high vulnerability published on June 9, 2026. Heap-based buffer overflow in Microsoft Office allows an unauthorized attacker to execute code locally.
When was CVE-2026-44824 disclosed?
CVE-2026-44824 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44824 actively exploited?
CVE-2026-44824 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44824?
CVE-2026-44824 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44824?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44824, 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-44824

Explore →

Is Your Infrastructure Affected by CVE-2026-44824?

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

Start Free Scan →Browse All CVEs