Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted Word document via phishing
-
DeliveryVictim opens malicious file
-
ExploitTrigger heap buffer overflow in Word parser
-
ExecutionExecute arbitrary code as current user
-
ImpactCompromise host and user data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution 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 crafted Word document (CVSS UI:R) - there is no server-side or zero-click network path despite the AV:N rating, because 'network' here refers to remote delivery of the malicious file, not a listening service. No authentication or prior privileges are needed on the target (PR:N), and default Office Word configurations are affected across the listed Windows and Mac builds. The principal limiting factors are: mandatory user interaction (the file must be opened, and Protected View / Mark-of-the-Web warnings or disabled macros may interpose a prompt), that code runs only in the opening user's context (S:U, no privilege escalation), and that SSVC marks the attack non-automatable, so mass/wormable exploitation is not feasible. |
| Impact | Signals are moderately but not maximally aligned. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R, C:H/I:H/A:H, 8.8 HIGH) describes a classic weaponized-document memory-corruption bug: no privileges needed, low complexity, but mandatory user interaction (UI:R) - the victim must open a crafted Word file. This UI:R requirement is the single most important risk-dampening factor and is corroborated by CISA SSVC, which rates Exploitation as 'none' (no public exploit identified at time of analysis) and Automatable as 'no' (consistent with a flaw that cannot be sprayed at scale because it needs a human to open an attachment). Technical Impact is 'total,' matching the C:H/I:H/A:H full compromise of the user context. The vulnerability is NOT in CISA KEV, and no POC is indicated, so there is no evidence of active exploitation. EPSS is not provided in the input, so near-term exploitation probability cannot be quantified here - treat its absence as missing data, not as a low score. Net: this is a genuinely serious client-side RCE in an extremely widespread product and should be patched promptly, but it is driven by social-engineering delivery (phishing with a malicious document) rather than unauthenticated wormable network exploitation, so it is a 'patch on normal priority cycle' issue rather than an emergency drop-everything KEV-class threat. |
| Exploit ScenarioDerived | An attacker emails or otherwise delivers a maliciously crafted Word document to a target and lures them into opening it (phishing/spear-phishing). On open, parsing the document triggers a heap-based buffer overflow (CWE-122) in Office Word, corrupting memory to execute arbitrary code in the context of the current user. No public exploit code is identified at time of analysis, and user interaction is required, so delivery depends on social engineering. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Heap-based buffer overflow in Microsoft Word allows remote attackers to execute code in the context of the user who opens a crafted Word document. Exploitation requires the victim to open an attacker-supplied file (CVSS UI:R) and no authentication or prior privileges (PR:N), with code running only in the opening user's context and no privilege escalation (S:U); SSVC marks the attack non-automatable, and no public exploit has been identified at time of analysis. Vendor patches are available, including fixed builds for Office LTSC 2021 and LTSC 2024, with updates for Mac and Microsoft 365 Apps distributed through Microsoft's Office security release channel.
RemediationAI
Apply the vendor patches identified by Microsoft: Office LTSC 2021 should be updated to 16.0.14334.20974 or later, and Office LTSC 2024 to 16.0.17932.21056 or later; for Microsoft Office LTSC for Mac 2021, Office LTSC for Mac 2024, Office 365 for Mac, and Microsoft 365 Apps for Enterprise, install the current update published through Microsoft AutoUpdate or the Office security release channel at https://aka.ms/OfficeSecurityReleases, and consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70287 for build-specific guidance. Where patching is delayed, keep Protected View and Mark-of-the-Web handling enabled for documents arriving from the internet or email and maintain macro-blocking policies, recognizing that these controls introduce user prompts and may interrupt legitimate document workflows; additionally, block or quarantine high-risk Word attachments at the email and web gateways and consider disabling embedded-object activation in Word via Group Policy, accepting that this can break documents that rely on embedded content. These compensating controls reduce exposure to the crafted-file delivery path but do not remove the underlying heap overflow, so the vendor update remains the primary fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 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 heap-based buffer overflow (CWE-122) in Microsoft Word's parsing of crafted document content, where a malformed structure causes an out-of-bounds write to heap memory that can corrupt adjacent data and potentially redirect execution. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H describes a remotely deliverable file (for example, an email attachment or web-hosted document) rather than a listening network service, so the AV:N rating reflects delivery of the malicious file; successful exploitation still demands user interaction to open it. Because the scope is unchanged, code executes with the privileges of the opening user on affected Office builds across Windows and macOS, and the SSVC assessment records exploitation as none, automatable as no, and technical impact as total. The relevant root-cause class is improper bounds checking on a heap buffer during document processing, which is consistent with the heap overflow label applied by the source tags.
Know when 365 Apps 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:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Malicious document is delivered remotely (AV:N) and parsing reliably triggers the overflow (AC:L) with no auth (PR:N), but the victim must open it (UI:R); code runs as the user (S:U) with full C/I/A impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code over a network.
Executive ViewAI
Microsoft Word contains a high-severity memory corruption flaw that could let an attacker take control of a user's Office session when they open a malicious document, putting sensitive data and business workflows at risk wherever Word files are exchanged with external parties. The issue requires user interaction, no public exploit has been identified at time of analysis, and vendor fixes are available; because Word is ubiquitous, leadership should prioritize rapid patching and document-handling controls to reduce exposure.
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
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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
Microsoft Outlook Remote Code Execution Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is remotel
Microsoft Excel Security Feature Bypass Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authenti
Microsoft Outlook Security Feature Bypass Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely
Microsoft Publisher Security Feature Bypass Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low att
Microsoft Office contains a security feature bypass (CVE-2026-21509, CVSS 7.8) where reliance on untrusted inputs in sec
Microsoft Office Word contains a security decision bypass (CVE-2026-21514, CVSS 7.8) through reliance on untrusted input
Microsoft Office Access Connectivity Engine Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vu
Microsoft Office Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentic
Microsoft Excel Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentica
Use-after-free vulnerability in Microsoft Office Word that allows local, unauthenticated attackers to execute arbitrary
Microsoft Excel Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely expl
Microsoft Office Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is low attack
EUVD-2026-99715
GHSA-rq9w-f72p-6m7r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB