Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious Office document
-
DeliveryDeliver via email or web to victim
-
ExploitVictim opens file in affected Office
-
ExecutionTrigger use-after-free in parser
-
ImpactExecute 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 a user to open an attacker-supplied malicious Office document (UI:R in the CVSS vector) on an affected Office build; the attacker needs no prior authentication or privileges on the target (PR:N), and the attack executes locally through the document rather than over the network (AV:L). Limiting factors: the mandatory user interaction means the victim must actually open the file and, for internet- or email-sourced documents, would typically need to dismiss Protected View / enable editing before the vulnerable code path is fully reachable, which substantially constrains mass exploitation. The bug affects both Windows and macOS Office builds listed in the CPE data, so platform is not a limiting factor, but only the enumerated Office versions are impacted. |
| Impact | The signals point to a realistic but not emergency-grade risk. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 7.8) reflects local attack vector with mandatory user interaction - the 'local' vector here means execution flows through a document the user must open, not remote network delivery, which materially lowers exploitability versus a wormable network bug. No EPSS score was supplied, and the vulnerability is not in CISA KEV, so there is no evidence of active exploitation; likewise no POC is referenced, meaning no public exploit is identified at time of analysis. The high triple-impact (C:H/I:H/A:H) shows full compromise of the user context is possible once exploited, and Office's enormous install base makes it an attractive phishing target, but the requirement for user interaction and the absence of exploitation evidence place this in the 'patch on normal cadence' tier rather than 'drop everything.' Note the reported tags include 'Denial Of Service' alongside code execution - the description and CVSS (C:H/I:H) emphasize code execution, so the DoS tag likely reflects a secondary crash outcome; verify with the vendor advisory if DoS-only impact matters to your assessment. |
| Exploit ScenarioDerived | An attacker emails or otherwise delivers a specially crafted Office document to a target and lures them into opening it (and, if applicable, exiting Protected View). Opening the file triggers the use-after-free, corrupting memory so the attacker's payload executes arbitrary code with the victim's privileges - typically the first foothold for credential theft or lateral movement. No public exploit is identified at time of analysis, so this reflects the plausible path given the AV:L/UI:R CVSS profile rather than an observed campaign. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Local code execution in Microsoft Office (2016, 2019, LTSC 2021/2024, Microsoft 365 Apps for Enterprise, and Office for Mac) stems from a use-after-free memory corruption (CWE-416) that an attacker triggers when a victim opens a maliciously crafted document. Rated CVSS 7.8 with high confidentiality, integrity, and availability impact, exploitation requires user interaction but no prior authentication, letting an attacker run arbitrary code in the context of the current user. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Microsoft has released a fix, so patching should be prioritized during the normal Patch Tuesday cycle.
RemediationAI
Apply the Microsoft-provided update for your Office channel; patch is available per vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55018 - the supplied data does not enumerate an exact fixed build, so pull the specific patched version for each SKU (Click-to-Run for Microsoft 365 Apps, MSI/LTSC packages, and the Mac AutoUpdate channel) directly from that MSRC page. Until updates are deployed, reduce exposure by enabling Protected View for files originating from the internet and email (the default, but confirm it is enforced by policy) and by blocking or gating untrusted Office attachments at the mail gateway, accepting the trade-off of added friction when users legitimately need to edit externally sourced documents. Because exploitation requires opening a crafted file, user-awareness guidance to not enable editing on unexpected documents is a meaningful interim control, though not a substitute for patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 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 flaw is a use-after-free (CWE-416), a memory-corruption class in which application code continues to reference an object after its backing memory has been freed, allowing an attacker who controls the freed-then-reallocated memory to hijack execution flow. The CPE data confirms the vulnerable component is the Microsoft Office application suite across Windows builds (Microsoft 365 Apps for Enterprise, Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024) and macOS builds (Office 365 for Mac, Office LTSC for Mac 2021 and 2024), indicating the defect lives in shared cross-platform Office parsing or object-lifecycle code rather than an OS-specific layer. Such bugs typically reside in the file-format parsers that deserialize complex document structures, where dangling pointers to freed document objects can be reclaimed by attacker-controlled data.
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:R/S:U/C:H/I:H/A:H
Exploitation is via opening a crafted document (AV:L, UI:R) with no prior privileges (PR:N); successful use-after-free yields code execution in user context, giving full C:H/I:H/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Use after free in Microsoft Office allows an unauthorized attacker to execute code locally.
Executive ViewAI
Microsoft Office contains a memory corruption vulnerability (CVE-2026-55018) that enables arbitrary code execution when employees open crafted documents, affecting versions 2016, 2019, LTSC 2021/2024, Microsoft 365 Apps, and Mac Office. This poses immediate risk to data confidentiality and system integrity across the organization, as successful exploitation requires only that a user open a malicious file-a highly probable attack vector given email and document sharing workflows. Microsoft has released a patch; timely deployment is critical to prevent ransomware, data exfiltration, and operational disruption.
Apply vendor patch.
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-44163
GHSA-65j6-99mv-3xg6
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB