Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Deliver crafted Word document to victim
  2. Delivery
    Victim opens file in vulnerable Word
  3. Exploit
    Trigger use-after-free in parser
  4. Execution
    Reclaim freed memory with controlled data
  5. Impact
    Execute arbitrary code as current user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

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 get a crafted Microsoft Word document onto the target and have it opened/processed locally by a vulnerable Word build (Word 2016, Office 2019, Office LTSC 2021/2024, Microsoft 365 Apps, or Office LTSC for Mac 2021/2024); code executes only in the context of the user opening the file. Limiting factors: the vector is local (AV:L), not network-remote, so delivery depends on email/download/social engineering; in practice a user must open the malicious document even though the published CVSS lists UI:N (this inconsistency should be verified with Microsoft); there is no privilege escalation implied (S:U), so the attacker gains only the victim's privileges; and there is no known active exploitation or public exploit code.

Impact

Signals are mixed and lean toward moderate real-world priority. CVSS is 8.4 (High) with total technical impact (C:H/I:H/A:H), but the vector is AV:L (local), meaning exploitation is not remotely network-reachable and typically requires the victim to open a crafted file. Notably, the CVSS vector lists UI:N (no user interaction) despite a local Word document-parsing bug that in practice would require a user to open a malicious document - this AV:L/UI:N combination is internally inconsistent and should be verified against the Microsoft advisory; the practical attack almost certainly involves user interaction. EPSS is very low (0.06%), CISA SSVC marks Exploitation as 'none' and Automatable 'no', and there is no KEV listing and no public exploit identified - so this is a real-but-not-urgent issue: patch on the normal Patch Tuesday cycle rather than as an emergency.

Exploit ScenarioDerived

An attacker emails or otherwise delivers a specially crafted Word document to a target; when the victim opens it, the malformed structure triggers the use-after-free in Word's parser, letting the attacker's controlled data steer freed-memory reuse and execute code as the logged-in user. Given AV:L this is a file-delivery/social-engineering attack rather than a remote network exploit, and no public proof-of-concept has been identified at time of analysis.

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 Office Word (2016, 2019, LTSC 2021/2024, Microsoft 365 Apps, and Office LTSC for Mac 2021/2024) arises from a use-after-free memory-corruption flaw that lets an attacker run arbitrary code in the context of the user who opens a maliciously crafted document. Microsoft has released a patch, and no public exploit has been identified at time of analysis; EPSS is very low at 0.06% (18th percentile) and CISA SSVC records no known exploitation.

RemediationAI

Apply the Microsoft update: Patch available per vendor advisory (MSRC), with confirmed fixed builds of Microsoft Word 2016 at 16.0.5552.1000 and Office LTSC for Mac 2021/2024 at 16.109.26051019; for click-to-run/365, LTSC 2021/2024, and Office 2019, install the current security build delivered through https://aka.ms/OfficeSecurityReleases and referenced at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40361. Where immediate patching is not possible, reduce exposure by opening untrusted documents in Protected View / Application Guard (which sandboxes parsing at the cost of disabling editing until the user explicitly trusts the file), blocking or quarantining Word documents from external email and web sources at the mail/proxy gateway (may delay legitimate business documents), and enforcing 'Block macros from the Internet' and Mark-of-the-Web handling - though note these macro controls do not directly stop a memory-corruption bug in the file parser and are only partial compensating controls.

Affected VersionsENISA

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 Office LTSC 2021 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2024 16.0.0 <https://aka.ms/OfficeSecurityReleases
Microsoft Office 2019 19.0.0 <https://aka.ms/OfficeSecurityReleases
Microsoft 365 Apps for Enterprise 16.0.1 <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-416 (Use After Free): Word's document-parsing/rendering engine frees a memory object but continues to reference the dangling pointer, allowing an attacker to reclaim that memory with controlled data and corrupt program state to hijack execution. This affects the shared Office Word code base across Windows builds (Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021/2024, Word 2016) and the macOS builds (Office LTSC for Mac 2021/2024) per the CPE set, indicating the vulnerable component is the cross-platform Word file-format handling code rather than an OS-specific module. The 'Denial Of Service' and 'Memory Corruption' tags are consistent with use-after-free, which can yield either a crash or, with a reliable heap groom, arbitrary code execution.

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

Vendor (microsoft) PRIMARY 8.4 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
CIRCL (temporal) 7.3 HIGH
vuln.today AI 7.8 HIGH

Local file-parsing use-after-free realistically needs the victim to open a crafted document, so AV:L and UI:R; no privileges required (PR:N), and successful exploitation yields full code execution as the user (C:H/I:H/A:H).

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 Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Use after free in Microsoft Office Word allows an unauthorized attacker to execute code locally.

Executive ViewAI

Why It Matters

Microsoft Office Word across eight supported versions (2016, 2019, LTSC 2021/2024, Microsoft 365 Apps, and Office LTSC for Mac 2021/2024) is vulnerable to local code execution when users open maliciously crafted documents (CVSS 8.4), affecting any organization with distributed Office deployments. Real-world exploitation likelihood is minimal (0.1% EPSS) with no public exploit or active attacks currently identified. A vendor patch is available.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 82% exploitable
Prevalence
Ubiquitous
Microsoft Word is deployed across the vast majority of enterprise environments
Threat Intel
2
1 sources
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
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

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

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.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

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