Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious Office document
-
DeliveryDelivers file to target via phishing or shared storage
-
ExploitTarget user opens document locally
-
ExecutionOut-of-bounds read triggered in Office parser
-
ImpactAdjacent memory contents disclosed
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a target user locally open a specially crafted Office document - user interaction (UI:R) is mandatory and cannot be bypassed remotely. The attack vector is local (AV:L), meaning the malicious file must already be present on or delivered to the target system; direct network-based exploitation without file delivery is not possible. No authentication or elevated privileges are required from the attacker's perspective (PR:N), but the attacker must successfully socially engineer the target into opening the file. Impact is limited to low confidentiality disclosure (C:L); no integrity or availability impact is possible from this vulnerability. Exploitation is further constrained by the non-automatable SSVC rating, meaning mass automated exploitation is not feasible. Protected View or Application Guard configurations in Office would block the vulnerable code path for documents from untrusted sources. |
| Impact | All available signals converge on very low real-world risk. CVSS 3.3 (AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) reflects a local, low-complexity attack requiring user interaction with impact limited to partial confidentiality loss. EPSS scores this at 0.36% exploitation probability in the 28th percentile, consistent with a low-severity information-disclosure class that rarely attracts weaponization effort. SSVC explicitly rates exploitation as none, automatable as no, and technical impact as partial - all low-tier signals. The vulnerability is not listed in CISA KEV and no POC has been identified. The one potential amplifier is product prevalence: Microsoft Office is ubiquitous, meaning the absolute number of potentially exposed endpoints is large even when individual risk is low. However, the attack's requirement for local file execution and user interaction creates a meaningful barrier to mass exploitation. There are no conflicting signals between data sources. |
| Exploit ScenarioDerived | An attacker sends a target a malicious Office document - via email attachment, shared drive, or web download - crafted to trigger an out-of-bounds read in the Office parser. When the victim opens the file, the parser reads beyond a buffer boundary and exposes a small region of process memory, which the attacker could potentially extract through a side channel embedded in the document's output behavior. No public POC exists; the CVSS local vector means this scenario requires the attacker to get the file onto the target system and have the user open it, limiting scalability compared to network-exploitable flaws. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Out-of-bounds read in Microsoft Office exposes a limited portion of process memory to a local attacker when a user opens a specially crafted document. Affected products span Office 2016 through LTSC 2024 on both Windows and macOS, with impact confined to low-severity information disclosure and no integrity or availability consequence. No public exploit code exists and CISA has not listed this in KEV; SSVC confirms exploitation status as none and the vulnerability is assessed as non-automatable, collectively placing this in the lowest real-world risk tier despite broad product coverage.
RemediationAI
Vendor-released patch is available. For Windows builds of Office 2016, upgrade to version 16.0.5561.1000 or later. For Office 2019, LTSC 2021, LTSC 2024, and Microsoft 365 Apps for Enterprise on Windows, apply the latest cumulative update via Microsoft Update or the Office Deployment Tool, referencing the current release table at https://aka.ms/OfficeSecurityReleases. For all Mac variants (Office 365 for Mac, LTSC for Mac 2021, LTSC for Mac 2024), upgrade to version 16.111.26071215 or later through Microsoft AutoUpdate or the Mac App Store. The Microsoft MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55139 is the authoritative source for patch availability per channel. If immediate patching is not feasible, the most effective compensating control is to configure Protected View or Application Guard in Office to open untrusted documents in an isolated environment, which prevents the vulnerable parser from executing in the user's primary context. Mark-of-the-Web enforcement (ensuring downloaded files retain their MOTW flag) also causes Office to open suspect files in Protected View by default, partially mitigating the attack path without requiring configuration changes.
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
CWE-125 (Out-of-bounds Read) describes a memory safety defect in which a parsing routine reads beyond the bounds of an allocated buffer, potentially exposing adjacent memory contents. In this case the flaw resides within Microsoft Office's document processing subsystem - consistent with the local attack vector and user-interaction requirement, which strongly imply a file-format parser triggered when a crafted document is opened. CPE strings confirm the affected surface spans cpe:2.3:a:microsoft:microsoft_office_2016, microsoft_office_2019, microsoft_office_ltsc_2021, microsoft_office_ltsc_2024, microsoft_365_apps_for_enterprise, and their Mac counterparts (microsoft_office_365_for_mac, microsoft_office_ltsc_for_mac_2021, microsoft_office_ltsc_for_mac_2024). The 'Buffer Overflow' tag is a mislabeling common in CVE tagging pipelines - the root cause is a read overflow, not a write overflow, so code execution is not implied by the CWE.
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:L/I:N/A:N
Local file-open trigger (AV:L, UI:R), no privilege required to open a document (PR:N), impact limited to partial memory read (C:L) with no integrity or availability consequence.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Out-of-bounds read in Microsoft Office allows an unauthorized attacker to disclose information locally.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-44217
GHSA-w2q4-mjj7-pcp4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB