Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious Word document
-
DeliveryUser opens file locally
-
ExploitTrigger use-after-free in parsing engine
-
ExecutionManipulate freed heap memory
-
PersistRedirect execution flow
-
ImpactExecute arbitrary code with user privileges
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 | The attacker must have local access to the Windows system running Microsoft Office Word. No user privileges required. No victim interaction needed — exploitation occurs automatically upon processing a malicious file or memory state. |
| Impact | The CVSS 8.4 score reflects high severity, driven by the combination of no required privileges (PR:N), no user interaction (UI:N), and complete system compromise potential (C:H/I:H/A:H). However, the local attack vector (AV:L) significantly constrains real-world exploitation scenarios-an attacker must already have local system access or convince a user to open a malicious document from a local file system. The low attack complexity (AC:L) indicates reliable exploitation once the malicious file is processed. Without EPSS data, exploitation probability remains theoretical, but the use-after-free primitive is well-understood by exploit developers and commonly targeted in memory corruption research. The absence of confirmed active exploitation (no KEV listing) and no public exploit code reduces immediate urgency compared to remotely exploitable vulnerabilities. The SSVC framework would likely classify this as 'scheduled' priority rather than 'immediate' for most organizations, unless users routinely process untrusted Office documents from external sources. The denial-of-service tag suggests reliability issues during exploitation attempts may cause application crashes before successful code execution, further reducing practical risk. Patch availability from Microsoft's official security update channel enables straightforward remediation, making this a manageable risk for organizations with functional patch management programs. |
| Exploit ScenarioDerived | An attacker crafts a malicious Word document (.docx or .doc) containing specially formatted objects that trigger the use-after-free condition during parsing. When a user opens the document locally-either from email attachment saved to disk, USB drive, network share, or cloud storage synchronized to the local filesystem-Word processes the malformed structures, freeing memory while retaining active pointers. The attacker's payload manipulates heap layout to control the freed memory region, redirecting execution to embedded shellcode that runs with the privileges of the Word process, typically the logged-in user. No public exploit code exists, but the low complexity rating suggests skilled attackers could develop reliable exploits given the detailed vulnerability class and affected component information. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
Memory corruption in Microsoft Office Word enables local code execution through a use-after-free flaw affecting Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 for Windows and Mac. Despite the local attack vector (AV:L), the vulnerability requires no privileges (PR:N) or user interaction (UI:N), allowing unauthorized attackers to execute arbitrary code with high impact to confidentiality, integrity, and availability (CVSS 8.4). Vendor-released patch available via Microsoft Security Response Center as of April 2026. No public exploit identified at time of analysis, though the technical simplicity (AC:L) and memory corruption primitive increase weaponization risk.
RemediationAI
Organizations should immediately apply security updates through Microsoft's official distribution channels. For macOS deployments, upgrade Microsoft Office LTSC for Mac 2021 and 2024 to version 16.108.26041219 or later. For Windows deployments of Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024, consult the April 2026 security release guidance at https://aka.ms/OfficeSecurityReleases for specific patched build numbers. Enterprise environments using Microsoft Update, WSUS, or Configuration Manager should deploy the corresponding security update packages. Until patching is complete, restrict processing of Office documents from untrusted sources and consider application-level sandboxing or virtualization for high-risk document workflows. Disable automatic preview features in Windows Explorer and Outlook to prevent inadvertent file processing. The Microsoft Security Response Center update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33115 provides complete remediation instructions and detection guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 7 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability stems from CWE-416 (Use After Free), a memory safety defect where the application continues to use a memory pointer after the referenced object has been deallocated. In Microsoft Word's document parsing or rendering engine, this occurs when processing specially crafted Office documents, causing the application to access freed heap memory. If an attacker can control the contents of the freed memory region through heap manipulation techniques (heap spraying, heap feng shui), they can redirect program execution flow to attacker-controlled code. The affected products span the entire modern Office ecosystem: Microsoft 365 Apps for Enterprise (version 16.0.1 and earlier), Office LTSC 2021 (version 16.0.1 and earlier), Office LTSC 2024 (version 16.0.0 and earlier), and their macOS equivalents. The CPE strings confirm this affects perpetual license products (LTSC) and subscription-based deployments (Microsoft 365), representing both enterprise and consumer installation bases across Windows and macOS platforms.
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
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Microsoft Office Word allows an unauthorized attacker to execute code locally.
Executive ViewAI
Microsoft Office Word contains a high-severity memory corruption vulnerability (CVE-2026-33115, CVSS 8.4) enabling local code execution without user interaction or elevated privileges, affecting Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 across Windows and Mac platforms. Any user with local system access can execute arbitrary code with full system compromise potential, creating immediate risk to data confidentiality, integrity, and availability across the organization.
Apply vendor patch. If immediate patching is not feasible: (1) restrict local system access through endpoint hardening and privileged access management; (2) monitor process execution and code injection attempts targeting Office processes via EDR solutions; (3) disable Office macro execution and external content loading as interim controls; (4) increase logging and alerting on Word process anomalies.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Local code execution in Microsoft Word (and Office/SharePoint components that render Word content) stems from an integer
Arbitrary code execution in Microsoft Office Word (and the broader Office/365/SharePoint family) arises from a stack-bas
Local code execution in Microsoft Word (part of Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, and Office for M
Arbitrary code execution in Microsoft PowerPoint (and the broader Microsoft Office/365 suite on Windows and macOS) arise
Local code execution in Microsoft Office PowerPoint (including Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, a
Local code execution in Microsoft Office PowerPoint (CWE-122 heap-based buffer overflow) lets an unauthorized attacker r
Local code execution in Microsoft Word (and the wider Microsoft Office / Microsoft 365 Apps family) lets an unauthorized
Local code execution in Microsoft Word (Office 2016/2019, Microsoft 365 Apps, Office LTSC 2021/2024) arises from a heap-
Local code execution in Microsoft Office Word (CWE-416 use-after-free) allows an unauthorized attacker to run arbitrary
Local code execution in Microsoft Office Word (Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Word 2016, and the macOS
Local code execution in Microsoft Office Word (via a stack-based buffer overflow, CWE-121) lets an attacker run arbitrar
Local code execution in Microsoft Office Word (across Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Office for Mac, an
EUVD-2026-22633
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB