Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain low-privileged local access
  2. Delivery
    Invoke vulnerable Office component
  3. Exploit
    Trigger use-after-free (CWE-416)
  4. Execution
    Reclaim freed object with controlled data
  5. Persist
    Hijack execution flow
  6. Impact
    Elevate privileges on host

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 local, already-authorized attacker: the CVSS vector AV:L with PR:L means the attacker must have local access and at least low-level (authenticated standard-user) privileges on the target host before triggering the flaw. No second-user interaction is needed (UI:N) and attack complexity is low (AC:L). The vulnerable code is present in default installations of the listed Office/Microsoft 365 desktop products, so no special non-default feature toggle is documented - the primary limiting factors are the need for prior local code-execution/login as a user and the requirement that a vulnerable, unpatched Office build be installed. This is not remotely reachable over a network without an existing local foothold.

Impact

Signals point to a genuine but not urgent priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U) shows a local vector requiring some existing privileges but low complexity and no user interaction, with total impact on confidentiality, integrity, and availability. Countervailing signals lower real-world urgency: EPSS is 0.04% (13th percentile), CISA SSVC lists Exploitation: none and Automatable: no, and there is no KEV listing and no public exploit identified at time of analysis - the SSVC Technical Impact of 'total' aligns with the CVSS impact metrics but does not by itself imply exploitation. One point to verify: the description characterizes this strictly as local privilege elevation, yet the CVSS assigns C:H/I:H/A:H with UI:N, which is broader than a pure DoS despite the 'Denial Of Service' tag - treat the elevation-of-privilege framing as authoritative from Microsoft and the impact metrics as the resulting worst case. Overall this is a standard-cadence patch item rather than an emergency, absent evidence of exploitation.

Exploit ScenarioDerived

An attacker who already has a low-privileged foothold on a workstation (for example via phishing malware or a standard user account) runs or opens specially crafted content that drives the vulnerable Office code path, triggering the use-after-free and manipulating the freed object to hijack execution and elevate privileges on the machine. No user interaction by a second victim is required per the CVSS vector (UI:N), and attack complexity is low, but no public exploit is identified at time of analysis, so this remains a plausible rather than demonstrated attack.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% 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 privilege elevation in Microsoft Office (Microsoft 365 Apps for Enterprise, Office 2019, and Office LTSC 2021/2024) stems from a use-after-free memory corruption flaw (CWE-416) that an already-authorized local attacker can trigger to gain higher privileges on the host. Microsoft has released a patch, and there is no public exploit identified at time of analysis; EPSS is very low (0.04%, 13th percentile) and CISA SSVC records exploitation as none, indicating no observed in-the-wild activity. The CVSS 3.1 base score is 7.8 with total technical impact (C:H/I:H/A:H) once triggered.

RemediationAI

Apply the Microsoft-released update for your Office channel; per the precision guidance this is 'Patch available per vendor advisory' - obtain the exact fixed build from the MSRC guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40419 and the Office security releases index at https://aka.ms/OfficeSecurityReleases, then match it to your servicing channel (Current Channel, Monthly Enterprise, or the LTSC/Office 2019 MSI builds). For click-to-run installs, ensure automatic updates are enabled and force an update; for volume-licensed Office 2019/LTSC deployments, push the corresponding security update through your patch-management system. Because exploitation requires an already-authenticated local user, compensating controls where immediate patching is not possible include enforcing least privilege on endpoints (do not run daily as local admin), restricting who can log on interactively to sensitive hosts, and keeping Office attack-surface-reduction and Protected View settings enabled - trade-off: these reduce but do not eliminate the local elevation risk and may affect macro/add-in workflows.

Affected VersionsENISA

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

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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): Office code frees a memory object but retains and later dereferences a dangling pointer to it, allowing an attacker who can influence the reallocated memory to corrupt program state and hijack execution flow within the Office process. The affected code is shared across the Office application suite, as reflected in the CPE data covering cpe:2.3:a:microsoft:microsoft_365_apps_for_enterprise, microsoft_office_2019, microsoft_office_ltsc_2021, and microsoft_office_ltsc_2024. Use-after-free bugs in document-parsing/rendering components are a recurring class in Office; the 'Denial Of Service' and 'Memory Corruption' tags are consistent with the availability impact, while the confidentiality and integrity impact reflect the potential to run attacker-controlled code in the security context targeted by the elevation.

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

Local privilege elevation by an authorized user gives AV:L/PR:L, no second-user interaction needed (UI:N), low complexity, and a use-after-free yielding total C/I/A impact within an unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/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
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Use after free in Microsoft Office allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Local privilege escalation in Microsoft Office (2019, LTSC 2021/2024, and Microsoft 365 Apps for Enterprise) could allow currently-authorized users to elevate system access to administrative levels, creating risk of unauthorized data access and lateral movement within corporate networks. A vendor patch is available and no active exploitation has been observed, enabling controlled remediation.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Prevalence
Ubiquitous
Microsoft Office/365 is installed across the vast majority of enterprise endpoints
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less 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.0%
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