Skip to content
Fencer Intel
high 8.4

CVE-2026-40367 json

Microsoft Word Remote Code Execution Vulnerability

published 5mo ago modified 14d ago also EUVD-2026-29649

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

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

Patch / fix

  • Microsoft Microsoft Office LTSC for Mac 2021 16.109.26051019
  • Microsoft Microsoft Office LTSC for Mac 2024 16.109.26051019
  • Microsoft Microsoft SharePoint Enterprise Server 2016 16.0.5552.1002
  • Microsoft Microsoft SharePoint Server 2019 16.0.10417.20128
  • Microsoft Microsoft SharePoint Server Subscription Edition 16.0.19725.20280
  • Microsoft Microsoft Word 2016 16.0.5552.1000

Is CVE-2026-40367 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
6mo ago

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft Office LTSC 2021
  • Microsoft Microsoft Office LTSC 2024
  • Microsoft Microsoft Office LTSC for Mac 2021
  • Microsoft Microsoft Office LTSC for Mac 2024
  • Microsoft Microsoft SharePoint Enterprise Server 2016
  • Microsoft Microsoft SharePoint Server 2019
  • Microsoft Microsoft SharePoint Server Subscription Edition
  • Microsoft Microsoft Word 2016

Classification

Weakness
  • CWE-822 Untrusted Pointer Dereference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.