Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious Word document
  2. Delivery
    Deliver via email or web
  3. Exploit
    Victim opens file in Word
  4. Execution
    Trigger type confusion in parser
  5. Persist
    Corrupt memory and hijack execution
  6. Impact
    Run arbitrary code as user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to deliver a maliciously crafted Word document to a vulnerable Office/Word installation (Word 2016, Office 2019, Office LTSC 2021/2024, Microsoft 365 Apps, or Office for Mac 2021/2024) and have it processed locally by the target - the attack surface is the local document-parsing path (AV:L), and code runs only in the context of the user who processes the file. Limiting factors: the vector is local rather than network-remote, exploitation yields only user-level privileges (no privilege escalation is described), and realistically the victim must open or preview the crafted document - note that although the CVSS vector states UI:N, a Word type-confusion RCE typically depends on the user opening the file, a discrepancy that should be verified against the MSRC advisory. No authentication bypass or special server configuration is documented as a prerequisite beyond a vulnerable, unpatched Office build.

Impact

The signals point to a serious-but-not-urgent priority. The CVSS 8.4 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and SSVC 'total' technical impact reflect that successful exploitation fully compromises confidentiality, integrity, and availability. However, several signals temper real-world risk: EPSS is only 0.15% (35th percentile), SSVC exploitation is 'none', Automatable is 'no', there is no KEV listing, and no public exploit is identified - so this is a high-severity issue without evidence of active or imminent mass exploitation. There is a notable inconsistency to verify: the CVSS vector states UI:N (no user interaction), yet a type-confusion RCE in Word is realistically triggered by a victim opening a crafted document, which normally implies UI:R - verify with the Microsoft advisory, as this affects how 'unauthenticated/no-interaction' the attack truly is. The 'Authentication Bypass' tag is also not reflected in the CWE (type confusion/memory corruption) or the description and should be treated as unconfirmed metadata.

Exploit ScenarioDerived

An attacker emails or hosts a specially crafted Word document that triggers the type-confusion condition in Word's parser when processed; because the vector is local (AV:L) with no privileges required, the victim opening or previewing the file causes attacker-controlled memory corruption that executes code in the user's security context. No public exploit is identified at time of analysis, so this remains a plausible rather than demonstrated attack path.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Local code execution in Microsoft Word (Office 2016 through Office LTSC 2024, Microsoft 365 Apps, and Office for Mac) results from a type-confusion flaw (CWE-843) that lets an unauthorized attacker run arbitrary code with the victim's privileges. Microsoft rates it CVSS 8.4 with total technical impact, but there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.15%, 35th percentile). CISA SSVC records exploitation status as none and the issue is not automatable, indicating no observed in-the-wild activity.

RemediationAI

Apply the Microsoft security updates referenced in MSRC advisory CVE-2026-40364 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40364); patches are available from the vendor. For Word 2016 update to at least build 16.0.5552.1000, and for Office LTSC for Mac 2021/2024 update to at least 16.109.26051019; for Microsoft 365 Apps, Office 2019, and Office LTSC 2021/2024 install the current channel update via https://aka.ms/OfficeSecurityReleases as click-to-run/servicing typically auto-updates. Until patches are deployed, reduce exposure by opening untrusted documents only in Protected View / Application Guard and not disabling it, blocking or quarantining Word documents from external email and web sources at the gateway, and using Office 'Block macros/untrusted content' policies; note that enforcing Protected View and blocking inbound Office files can disrupt legitimate document workflows and should be scoped to untrusted sources.

Affected VersionsENISA

Microsoft Office LTSC 2021 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Word 2016 16.0.1 <16.0.5552.1000
Microsoft Office LTSC for Mac 2024 16.0.0 <16.109.26051019
Microsoft Office LTSC for Mac 2021 16.0.1 <16.109.26051019
Microsoft 365 Apps for Enterprise 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Office 2019 19.0.0 <https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2024 16.0.0 <https://aka.ms/OfficeSecurityReleases

Affected Packages

euvd microsoft_office_ltsc_for_mac_2021 fix: 16.109.26051019
euvd microsoft_office_ltsc_for_mac_2024 fix: 16.109.26051019
euvd microsoft_word_2016 fix: 16.0.5552.1000

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-843, 'Access of Resource Using Incompatible Type' (type confusion), in Microsoft Word's document parsing engine. Type confusion occurs when code allocates or interprets a memory object as one type but later accesses it as an incompatible type, allowing an attacker to manipulate pointers, function tables, or object fields and coerce the parser into treating attacker-controlled data as trusted structures - a memory-corruption primitive that commonly leads to arbitrary code execution. The CPE data confirms the affected surface is the Word/Office application layer across Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021/2024, Word 2016, and Office LTSC for Mac 2021/2024, meaning the flawed parsing code is shared across both Windows and macOS Office builds.

Know when Microsoft 365 Apps For Enterprise gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.4 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 7.8 HIGH

Local document-parsing flaw requiring a victim to open a crafted file, so AV:L and UI:R; no privileges needed (PR:N) and full type-confusion RCE yields C/I/A High.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

A type-confusion vulnerability in Microsoft Office (CVE-2026-40364, CVSS 8.4) enables local code execution in Word across Office 2016 through Office LTSC 2024, Microsoft 365 Apps, and macOS platforms. The vulnerability affects most organizations with broad Office deployments and could allow privilege escalation if exploited; however, current exploitation activity is low (0.1% EPSS) with no public exploit identified. A vendor patch is available, providing an immediate remediation path.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 65% exploitable
Prevalence
Ubiquitous
Microsoft Word/Office is deployed across the vast majority of enterprise endpoints
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More Likely
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

CVE-2026-55033 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (and Office/SharePoint components that render Word content) stems from an integer

CVE-2026-55038 HIGH
7.8 Jul 14

Arbitrary code execution in Microsoft Office Word (and the broader Office/365/SharePoint family) arises from a stack-bas

CVE-2026-55132 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (part of Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, and Office for M

CVE-2026-55120 HIGH
7.8 Jul 14

Arbitrary code execution in Microsoft PowerPoint (and the broader Microsoft Office/365 suite on Windows and macOS) arise

CVE-2026-55123 HIGH
7.8 Jul 14

Local code execution in Microsoft Office PowerPoint (including Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, a

CVE-2026-55043 HIGH
7.8 Jul 14

Local code execution in Microsoft Office PowerPoint (CWE-122 heap-based buffer overflow) lets an unauthorized attacker r

CVE-2026-55127 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (and the wider Microsoft Office / Microsoft 365 Apps family) lets an unauthorized

CVE-2026-55130 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (Office 2016/2019, Microsoft 365 Apps, Office LTSC 2021/2024) arises from a heap-

CVE-2026-55128 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (CWE-416 use-after-free) allows an unauthorized attacker to run arbitrary

CVE-2026-55134 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Word 2016, and the macOS

CVE-2026-55055 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (via a stack-based buffer overflow, CWE-121) lets an attacker run arbitrar

CVE-2026-55032 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (across Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Office for Mac, an

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy