Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Craft malicious Office document
  2. Delivery
    Deliver via email or file share
  3. Exploit
    User opens file in Office
  4. Execution
    Trigger use-after-free on freed object
  5. Persist
    Hijack control flow via reclaimed heap
  6. 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 victim to open an attacker-supplied malicious Office document on the local machine (AV:L with UI:R) - the attacker cannot trigger the flaw remotely without user action. No authentication or elevated privileges are needed on the attacker's part (PR:N), and the flaw affects default Office installations, so no special product feature or non-default configuration is required to be vulnerable. The primary limiting factors are the mandatory user interaction of opening the crafted file and the fact that code runs only at the current user's privilege level (S:U), meaning Protected View, sandboxing, or a low-privilege user account each meaningfully constrain real-world impact.

Impact

The CVSS 3.1 base score is 7.8 (High) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - local attack vector, low complexity, no privileges required, but mandatory user interaction (opening a file). This is a classic 'open a malicious document' profile: high impact if triggered, but gated behind social engineering rather than remote self-propagation. No EPSS score, SSVC decision, POC, or KEV signal was provided in the input, so exploitation probability cannot be quantified from the data; the absence of KEV means no confirmed active exploitation. Note the tag set includes 'Denial Of Service' which is narrower than the CVSS C:H/I:H/A:H code-execution impact - the CVSS and MSRC framing of code execution should be treated as authoritative over the tag. Overall this is a legitimately high-priority patch given Office's ubiquity and the low technical bar to exploit once a user opens the file, but it is not a network-wormable emergency.

Exploit ScenarioDerived

An attacker emails a crafted Office document (or hosts it on a web/file share) and uses social engineering to get a target to open it; the file contains malformed structures that trigger the use-after-free, corrupting the heap and executing attacker code in the user's security context. No public exploit is identified at time of analysis, and exploitation requires the victim to open the file (UI:R) rather than any remote trigger.

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

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

Alert me

AnalysisAIv1 – Jul 14, 2026

Local code execution in Microsoft Office (2016, 2019, LTSC 2021/2024, Microsoft 365 Apps, and Office for Mac 2021/2024) arises from a use-after-free memory corruption flaw that an attacker triggers by convincing a user to open a maliciously crafted Office document. Successful exploitation runs arbitrary code in the context of the current user, yielding full confidentiality, integrity, and availability impact on the host. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV; Microsoft has published a patch via MSRC.

RemediationAI

Apply the Microsoft-released update for your Office channel as the primary fix - Patch available per vendor advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50467); ensure Microsoft 365 Apps and Office 2016/2019/LTSC 2021/LTSC 2024 on Windows and the Office for Mac 2021/2024 builds all receive the corresponding security update, and confirm the exact patched build number from the MSRC page since the input did not specify one. Until patching completes, reduce exposure by opening untrusted documents in Protected View / Application Guard (which sandboxes the parsing that triggers the use-after-free), blocking or quarantining Office attachments from external senders at the mail gateway, and enabling Attack Surface Reduction rules that constrain Office child-process creation; the trade-off is that Protected View and ASR rules can disrupt legitimate macro-enabled or automation workflows and may require user retraining. These are compensating controls only - they do not remove the underlying flaw, so prioritize the update.

Affected VersionsENISA

Microsoft Office LTSC for Mac 2024 16.0.0 <16.111.26071215
Microsoft Office LTSC 2021 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC for Mac 2021 16.0.1 <16.111.26071215
Microsoft Office 2019 19.0.0 <https://aka.ms/OfficeSecurityReleases
Microsoft 365 Apps for Enterprise 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Office 2016 16.0.0 <16.0.5561.1000
Microsoft Office LTSC 2024 16.0.0 <https://aka.ms/OfficeSecurityReleases
Microsoft Office 365 for Mac 1.0.0 <16.111.26071215

Affected Packages

microsoft 365_apps_for_enterprise_https_aka_ms_officesecurityreleases fix: Microsoft 365 Apps for Enterprise for 32-bit Systems https://aka.ms/OfficeSecurityReleases, Microsoft 365 Apps for Enterprise for 64-bit Systems https://aka.ms/OfficeSecurityReleases
microsoft office_2016_32_bit_edition_16_0_5561_1000 fix: Microsoft Office 2016 (32-bit edition) 16.0.5561.1000
microsoft office_2016_64_bit_edition_16_0_5561_1000 fix: Microsoft Office 2016 (64-bit edition) 16.0.5561.1000
microsoft office_2019_editions_https_aka_ms_officesecurityreleases fix: Microsoft Office 2019 for 32-bit editions https://aka.ms/OfficeSecurityReleases, Microsoft Office 2019 for 64-bit editions https://aka.ms/OfficeSecurityReleases
microsoft office_365_for_mac_16_111_26071215 fix: Microsoft Office 365 for Mac 16.111.26071215
microsoft office_ltsc_2021_editions_https_aka_ms_officesecurityreleases fix: Microsoft Office LTSC 2021 for 32-bit editions https://aka.ms/OfficeSecurityReleases, Microsoft Office LTSC 2021 for 64-bit editions https://aka.ms/OfficeSecurityReleases
microsoft office_ltsc_2024_editions_https_aka_ms_officesecurityreleases fix: Microsoft Office LTSC 2024 for 32-bit editions https://aka.ms/OfficeSecurityReleases, Microsoft Office LTSC 2024 for 64-bit editions https://aka.ms/OfficeSecurityReleases
microsoft office_ltsc_for_mac_2021_16_111_26071215 fix: Microsoft Office LTSC for Mac 2021 16.111.26071215
microsoft office_ltsc_for_mac_2024_16_111_26071215 fix: Microsoft Office LTSC for Mac 2024 16.111.26071215
euvd microsoft_office_2016 fix: 16.0.5561.1000
euvd microsoft_office_365_for_mac fix: 16.111.26071215
euvd microsoft_office_ltsc_for_mac_2021 fix: 16.111.26071215
euvd microsoft_office_ltsc_for_mac_2024 fix: 16.111.26071215

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 13 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

The root cause is CWE-416 (Use After Free): the Office application frees a heap object but retains and later dereferences a dangling pointer to it, allowing an attacker who controls document contents to reclaim the freed allocation with attacker-influenced data and hijack program flow. The affected code is the Office document-parsing/rendering engine shared across the Windows builds (Microsoft 365 Apps for Enterprise, Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024 per the CPE list) and the macOS builds (Office 365/LTSC for Mac 2021 and 2024), indicating the vulnerable component is a cross-platform Office library rather than a Windows-only OS dependency. Use-after-free bugs in complex file-format parsers are a recurring memory-corruption class in Office and are typically reached through crafted structures embedded in a document.

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 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
CIRCL (temporal) 6.8 MEDIUM
vuln.today AI 7.8 HIGH

Local file-open vector so AV:L and UI:R; no attacker privileges needed (PR:N); code runs as the user with full C/I/A impact and no scope change.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

A vulnerability affecting all versions of Microsoft Office enables complete compromise of user systems through maliciously crafted documents, impacting organizations' core productivity tools and data security across their workforce. Attackers gaining control of employee systems can steal data, modify files, and pivot laterally to other systems within the organization's network. Although no public exploit code currently exists, organizations should prioritize immediate patching to close this significant attack vector before exploitation becomes widespread.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
Ubiquitous
Microsoft Office is deployed across the vast majority of enterprise endpoints
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 Less Likely
Data Quality
6 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.3%
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

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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