Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft document with attacker-controlled UNC path
-
DeliveryDeliver document via phishing or shared storage
-
ExploitVictim opens Word document
-
ExecutionWord resolves external file path automatically
-
PersistOutbound SMB/WebDAV request to attacker server
-
ImpactAttacker captures NTLM hash or file metadata
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
|
| Exploitation Conditions | Exploitation requires the victim user to open or preview a specially crafted Word document (UI:R per CVSS vector) - exploitation cannot occur without this user interaction, and the attack is confirmed not automatable per SSVC assessment. The attacker must be able to deliver the document to the target (e.g., via email attachment, download link, or shared drive) and must have network reachability to receive the outbound connection triggered by the malicious file path reference. No attacker authentication to the target system is required (PR:N per CVSS vector). No non-default configuration appears required - the flaw affects standard Word installations across all listed product versions. Exploitation is limited by: the mandatory user interaction (opening the file), the absence of code execution capability (information disclosure only), and network controls blocking outbound SMB/WebDAV to untrusted hosts. These limiting factors make this a lower-priority item despite the broad Office deployment footprint. |
| Impact | The CVSS 3.1 base score of 4.3 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N reflects a low-complexity, network-reachable attack requiring no attacker authentication but mandating user interaction - the victim must open or preview the malicious document. Confidentiality impact is limited (C:L) with no integrity or availability consequences. These signals are internally consistent: the SSVC assessment independently confirms exploitation status as 'none,' the attack is not automatable, and technical impact is partial only. EPSS at 0.05% (14th percentile) is very low, indicating this flaw is not being actively scanned or exploited at scale. No POC has been identified and CISA KEV listing is absent. Despite the ubiquitous deployment footprint of Microsoft Office, real-world priority is low-to-moderate: this is a targeted, user-interaction-gated information disclosure, not a wormable or remote code execution class vulnerability. The main risk elevation scenario is credential-theft (NTLM relay) when combined with attacker-controlled network infrastructure, which could increase impact beyond the raw CVSS score suggests if chained with lateral movement. |
| Exploit ScenarioDerived | An attacker sends a phishing email to a target employee containing a malicious Word document with an embedded UNC path (e.g., \\attacker.example.com\share\lure.docx) referencing an attacker-controlled SMB server. When the victim opens the document, Word automatically attempts to resolve the path, triggering an outbound SMB authentication request that delivers the victim's NTLM hash to the attacker's server, which can then be cracked offline or used in an NTLM relay attack. No public proof-of-concept code has been identified at time of analysis, but this UNC-coercion technique is a well-documented Office attack class requiring no special tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
External control of file name or path (CWE-73) in Microsoft Office Word enables network-based information disclosure when a victim opens a specially crafted document, affecting Word 2016, Office 2019, LTSC 2021/2024, and Microsoft 365 Apps for Enterprise. An unauthenticated remote attacker can exploit this to coerce Word into resolving an attacker-controlled file path - likely a UNC path - causing an outbound network request that leaks sensitive data such as NTLM credentials. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS score of 0.05% at the 14th percentile indicates negligible real-world exploitation activity at time of analysis.
RemediationAI
The primary fix is to apply Microsoft's security update for the affected Office product. For Microsoft Word 2016, update to build 16.0.5552.1000 or later - this is the only product for which a specific confirmed fix build number is available from EUVD data. For Microsoft Office 2019, LTSC 2021, LTSC 2024, and Microsoft 365 Apps for Enterprise, apply the patches documented at https://aka.ms/OfficeSecurityReleases as directed by the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40421. As a compensating control prior to patching, administrators can disable automatic resolution of external content in Word via Trust Center settings (File → Options → Trust Center → Trust Center Settings → External Content → Disable all external content), which will prevent Word from initiating outbound file-path resolution; the trade-off is that legitimate linked content and external data connections in documents will also be blocked. Additionally, network-level blocking of outbound SMB (TCP 445) and WebDAV (TCP 80/443) to untrusted external hosts will limit the data exfiltration path, though this may impact legitimate business workflows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 7 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
CWE-73 (External Control of File Name or Path) describes a weakness where an application constructs file paths using externally-supplied input without adequate neutralization, allowing an attacker to redirect file resolution to unintended locations. In Microsoft Office Word, this class of flaw is classically exploited via crafted document objects (e.g., OLE links, embedded objects, or template references) that embed attacker-controlled UNC paths (e.g., \\attacker-server\share\file), causing the application to initiate an SMB or WebDAV connection to an external host. This outbound connection can expose the victim's NTLM authentication hash or confirm file system metadata. The affected products are confirmed via CPE: cpe:2.3:a:microsoft:microsoft_word_2016, cpe:2.3:a:microsoft:microsoft_office_2019, cpe:2.3:a:microsoft:microsoft_office_ltsc_2021, cpe:2.3:a:microsoft:microsoft_office_ltsc_2024, and cpe:2.3:a:microsoft:microsoft_365_apps_for_enterprise, spanning the full currently-supported Microsoft Office on-premises and subscription portfolio.
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
Sources disagree (Low–High)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Network-delivered via crafted document with no attacker privileges; user must open the file; impact is limited to partial confidentiality disclosure with no integrity or availability consequence.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: microsoft
DescriptionCVE.org
External control of file name or path in Microsoft Office Word allows an unauthorized attacker to disclose information over a network.
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
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-29678
GHSA-m493-43x7-h3mj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB