CVE-2026-44818

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Office Excel allows an unauthorized attacker to execute code locally.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 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-44818

Vendor Advisories for CVE-2026-44818(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 8× in last 7d / 54× 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 333 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44818?
CVE-2026-44818 is a high vulnerability published on June 9, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Office Excel allows an unauthorized attacker to execute code locally.
When was CVE-2026-44818 disclosed?
CVE-2026-44818 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44818 actively exploited?
CVE-2026-44818 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 81.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44818?
CVE-2026-44818 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44818, 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-44818

Explore →

Is Your Infrastructure Affected by CVE-2026-44818?

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