CVE-2026-45456

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Access of resource using incompatible type ('type confusion') in Microsoft Office allows an unauthorized attacker to execute code locally.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
microsoftMentions a patch (unverified)

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-45456

Vendor Advisories for CVE-2026-45456(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 7× in last 7d / 28× 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 370 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45456?
CVE-2026-45456 is a high vulnerability published on June 9, 2026. Access of resource using incompatible type ('type confusion') in Microsoft Office allows an unauthorized attacker to execute code locally.
When was CVE-2026-45456 disclosed?
CVE-2026-45456 was first published on June 9, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45456 actively exploited?
CVE-2026-45456 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45456?
CVE-2026-45456 has a CVSS base score of 8.4 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-45456?
A fix for CVE-2026-45456 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-45456 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45456

Explore →

Is Your Infrastructure Affected by CVE-2026-45456?

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